linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: 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:58:58 +0200	[thread overview]
Message-ID: <20030729095858.GB1286@louise.pinerecords.com> (raw)
In-Reply-To: <20030729094820.GC28348@werewolf.able.es>

> [jamagallon@able.es]
> 
> > The latest prepatch for the stable Linux kernel tree is: 2.4.22-pre8
> 
> So what it this -------------------------------------------^^^^^^ ??

Does your screen only have 63 columns?

> 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.

Try submitting a bug report that reads "there's this and this problem
in 2.4.22."  One of the first questions you are bound to be asked is
"could you clarify the version you're seeing the problem with?"

> I hope you just use release kernels, -pres are only for Mandrake people ;)

Does Mandrake also ship "stable" distributions w/ kernels compiled using
gcc 3.3-whatever or is that idiocy suse-specific?

> 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.

So far I said nothing about the problem itself; all the time I'm merely
trying to point out that it's dreadfully unreasonable to pretend that
there's a gcc 3.3.1.

> Linux 2.4.22-pre8-jam1m (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-0.6mdk))

Right.

-- 
Tomas Szepe <szepe@pinerecords.com>

  reply	other threads:[~2003-07-29  9:59 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 [this message]
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=20030729095858.GB1286@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=jamagallon@able.es \
    --cc=kwall@kurtwerks.com \
    --cc=lcapitulino@prefeitura.sp.gov.br \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).