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 11:48:20 +0200 [thread overview]
Message-ID: <20030729094820.GC28348@werewolf.able.es> (raw)
In-Reply-To: <20030729093521.GA1286@louise.pinerecords.com>; from szepe@pinerecords.com on Tue, Jul 29, 2003 at 11:35:21 +0200
On 07.29, Tomas Szepe wrote:
> > On 07.29, Tomas Szepe wrote:
> >
> > Then why are we all calling current kernel 2.4.22 instead of
2.4.21.90 ?
>
> WE aren't.
>
> www.kerne.org:
> The latest stable version of the Linux kernel is: 2.4.21
> The latest prepatch for the stable Linux kernel tree is: 2.4.22-pre8
So what it this -------------------------------------------^^^^^^ ??
If people talks to you about 2.4.22, sure you understand at the first
glance tyey talk about the -pre of 2.4.22.
> The latest snapshot for the stable Linux kernel tree is: 2.4.21-bk20
>
> > OK, the full name would be gcc-3.3.1-prerelease-of-20030720.
>
> Yeah, it doesn't really surprise me it's all the same to Mandrake
people.
>
What about Mandrake people ? Whats wrong with testing prerelease
software ?
I hope you just use release kernels, -pres are only for Mandrake people
;)
I would understand you if it were a bug in the compiler, if it it cried
against obviously correct code, but it just says
that the assembler syntax is old and you should change it.
Any ways, let it be. You just will have to hurry when real 3.3.1 or 3.4
gets out, and then two thousand people complaint instead of two couples.
--
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 9:50 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 [this message]
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
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=20030729094820.GC28348@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