From: Luke-Jr <luke-jr@gentoo.org>
To: Donnie Berkholz <spyderous@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Patches and the 2.4->2.6 move
Date: Mon, 20 Oct 2003 04:04:40 +0000 [thread overview]
Message-ID: <200310200404.49367.luke-jr@gentoo.org> (raw)
In-Reply-To: <1066620130.5592.17.camel@sfa237013.richmond.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 20 October 2003 03:22 am, Donnie Berkholz wrote:
> Forgot to answer this:
> "Fix NASM problems, remove static var in SSE detection code. (Josh
> Vanderhoof)"
>
> It fixes problems in SSE and 3Dnow detection.
But why doesn't it work the same with both 2.4 and 2.6? Is it a bug in 2.4 or
2.6 that makes them react differently/poorly?
- --
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/k17fZl/BHdU+lYMRAsw3AJ0bzxsQ6B0DhrUgTOP/27sPhDd/cgCcC8Z+
/j3K7zfj22cO4CBBKDWvCh4=
=B3EZ
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-20 4:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 2:34 [gentoo-dev] Patches and the 2.4->2.6 move Donnie Berkholz
2003-10-20 3:05 ` Luke-Jr
2003-10-20 3:18 ` Donnie Berkholz
2003-10-20 3:22 ` Donnie Berkholz
2003-10-20 4:04 ` Luke-Jr [this message]
2003-10-20 4:30 ` Donnie Berkholz
2003-10-20 3:20 ` Brandon Hale
2003-10-20 3:25 ` Donnie Berkholz
2003-10-20 4:32 ` Luke-Jr
2003-10-20 4:16 ` Luke-Jr
2003-10-20 3:38 ` Jason Stubbs
2003-10-20 4:25 ` Jon Portnoy
2003-10-20 4:33 ` Kumba
2003-10-20 4:59 ` Donnie Berkholz
2003-10-19 23:48 ` C. Brewer
2003-10-20 7:13 ` Luke-Jr
2003-10-20 0:30 ` C. Brewer
2003-10-20 5:15 ` Luke-Jr
2003-10-20 5:23 ` Donnie Berkholz
2003-10-20 13:47 ` Alexander Gretencord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200310200404.49367.luke-jr@gentoo.org \
--to=luke-jr@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=spyderous@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox