From: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6-test2: gcc-3.3.1 warning.
Date: 29 Jul 2003 12:57:52 +0100 [thread overview]
Message-ID: <1059479661.3118.5.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030729102007.GC1286@louise.pinerecords.com>
On Maw, 2003-07-29 at 11:20, Tomas Szepe wrote:
> > 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.
>
> Large. 3.3 is a development series. It DOES introduce new stuff.
>
> In production environments you definitely want to stick with 3.2.3
> or (better yet) 2.95.3.
3.2 is probably the best, but lots of people are using gcc 3.3 to build
kernels and so far all the things we've hit have been the stricter
parser throwing up on technically invalid C in the kernel source/
next prev parent reply other threads:[~2003-07-29 12:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 12:40 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
2003-07-29 10:20 ` Tomas Szepe
2003-07-29 11:57 ` Alan Cox [this message]
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=1059479661.3118.5.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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
all inboxes | Powered by JetHome®