linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: marcelo@conectiva.com.br, jgarzik@pobox.com,
	linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
	torvalds@osdl.org
Subject: Re: RFC:  what's in a stable series?
Date: Thu, 10 Jul 2003 01:25:49 -0700	[thread overview]
Message-ID: <20030710012549.7624b397.akpm@osdl.org> (raw)
In-Reply-To: <20030710085325.A28672@infradead.org>

Christoph Hellwig <hch@infradead.org> wrote:
>
> Especially
>  when just changing a function arg where you only get one more warning in
>  the forrest of warnings produced by gcc 3.3 on a 2.4 tree..

Switching topics (to one of my favourites):

This is a perfect demonstration of why it is utterly unacceptable for
compiler developers to add new warnings without also providing a way of
turning them off.


  reply	other threads:[~2003-07-10  8:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10  1:06 RFC: what's in a stable series? Jeff Garzik
2003-07-10  1:08 ` Jeff Garzik
2003-07-10  3:34 ` Herbert Pötzl
2003-07-10  7:53   ` Christoph Hellwig
2003-07-10 11:22   ` Alan Cox
2003-07-10 12:36     ` Herbert Pötzl
2003-07-10  3:54 ` Greg KH
2003-07-10  3:54 ` Marcelo Tosatti
2003-07-10  4:16   ` Andrew Morton
2003-07-10  7:53     ` Christoph Hellwig
2003-07-10  8:25       ` Andrew Morton [this message]
2003-07-10  7:53   ` Christoph Hellwig
2003-07-10 11:19     ` Alan Cox
2003-07-10 12:13       ` Marcelo Tosatti
2003-07-10 12:42         ` Alan Cox
2003-07-10 15:15           ` Christoph Hellwig
2003-07-10 19:00             ` Jan Kara
2003-07-11  8:36               ` Christoph Hellwig
2003-07-11  9:21             ` Alan Cox
2003-07-10 15:12         ` Christoph Hellwig
2003-07-10 15:11       ` Christoph Hellwig

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=20030710012549.7624b397.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@osdl.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).