From: "J.A. Magallon" <jamagallon@able.es>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Kurt Wall <kwall@kurtwerks.com>,
Luiz Capitulino <lcapitulino@prefeitura.sp.gov.br>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6-test2: gcc-3.3.1 warning.
Date: Tue, 29 Jul 2003 12:11:26 +0200 [thread overview]
Message-ID: <20030729101126.GC29124@werewolf.able.es> (raw)
In-Reply-To: <20030729095858.GB1286@louise.pinerecords.com>; from szepe@pinerecords.com on Tue, Jul 29, 2003 at 11:58:58 +0200
On 07.29, Tomas Szepe wrote:
[...]
>
> Does Mandrake also ship "stable" distributions w/ kernels compiled
using
> gcc 3.3-whatever or is that idiocy suse-specific?
>
Tell me a distro that ships pristine www.kernel.org kernels o release
gcc's,
without any 'backported patch from xxx-1234 to correct PR1234'. What is
the difference between backporting a patch from 3.3.1-pre to 3.3, and
using 3.3.1-pre directly ? Ah, that you get less bug corrected.
And no, at least in my case, this is not a stable Mandrake, it is
Cooker,
the equivalent of RawHide. Latest stable shiped a kernel built with
3.2.3,
and current cooker builds kernels with 3.3.1. And bugs are discovered
and
fixed. What's bad ?
--
J.A. Magallon <jamagallon@able.es> \ Software is
like sex:
werewolf.able.es \ It's better when
it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.22-pre8-jam1m (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-0.6mdk))
next prev parent reply other threads:[~2003-07-29 10:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 12:40 2.6-test2: gcc-3.3.1 warning Luiz Capitulino
2003-07-28 20:29 ` Randy.Dunlap
2003-07-28 22:50 ` Tomas Szepe
2003-07-29 0:22 ` Kurt Wall
2003-07-29 4:55 ` Tomas Szepe
2003-07-29 9:28 ` J.A. Magallon
2003-07-29 9:35 ` Tomas Szepe
2003-07-29 9:48 ` J.A. Magallon
2003-07-29 9:58 ` Tomas Szepe
2003-07-29 10:11 ` J.A. Magallon [this message]
2003-07-29 10:20 ` Tomas Szepe
2003-07-29 11:57 ` Alan Cox
2003-07-29 15:35 ` Randy.Dunlap
2003-08-17 1:25 ` Richard Henderson
2003-08-17 1:34 ` Linus Torvalds
2003-08-17 2:04 ` Randy.Dunlap
2003-07-29 12:34 ` Jakub Jelinek
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=20030729101126.GC29124@werewolf.able.es \
--to=jamagallon@able.es \
--cc=kwall@kurtwerks.com \
--cc=lcapitulino@prefeitura.sp.gov.br \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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