public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18
Date: Tue, 26 Feb 2002 17:46:02 +0100	[thread overview]
Message-ID: <20020226174602.4f4b30bc.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0202251613300.31438-100000@freak.distro.conectiva>
In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C01101FE2@nocmail.ma.tmpw.net> <Pine.LNX.4.21.0202251613300.31438-100000@freak.distro.conectiva>

On Mon, 25 Feb 2002 16:18:46 -0300 (BRT)
Marcelo Tosatti <marcelo@conectiva.com.br> wrote:

> [...]
> The patch which I missed only breaks static apps on _some_ architectures
> (not including x86).

This statement is not very nice. You obviously classify these architectures as minor important. At least not important enough to give them a release version as bugfree as possible at the given time. You shouldn't do that, don't focus on what you classify the "mainstream" too much. 
As stated before, there is no problem with making mistakes. You only have to handle the situation in an intelligent manner _and_ aware of the power given to you. 
In my eyes, the clean choice would have been 2.4.19 release.

> > Some people may get confused grabbing 2.4.18 and not getting the fixes
> > that went into rc-4? Just a thought...
> 
> I already changed ftp.kernel.org's changelog adding:
> 
> "Update: The SET_PERSONALITY fix in rc4 has _not_ 
> been included in the final 2.4.18 by mistake."
> 
> I guess thats enough.

Technically correct, but intentionally questionable.

Regards,
Stephan


  parent reply	other threads:[~2002-02-26 16:46 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 20:20 Linux 2.4.18 Holzrichter, Bruce
2002-02-25 19:18 ` Marcelo Tosatti
2002-02-24  5:08   ` Daniel Phillips
2002-02-25 20:37   ` DevilKin
2002-02-25 20:45     ` Thomas Glanzmann
2002-02-25 21:29     ` John Stoffel
2002-02-25 21:54       ` Mike Fedyk
2002-02-25 21:57         ` John Stoffel
2002-02-25 22:05         ` David S. Miller
2002-02-25 22:58         ` Bernd Eckenfels
2002-02-26  0:19       ` Harald Arnesen
2002-02-25 22:56   ` Bernd Eckenfels
2002-02-26  0:22     ` Harald Arnesen
2002-02-26  0:28       ` Eric Krout
2002-02-26  3:06         ` Andreas Dilger
2002-02-26 16:46   ` Stephan von Krawczynski [this message]
2002-02-26 17:13     ` Rik van Riel
2002-02-26 17:50       ` Stephan von Krawczynski
2002-02-26 19:42     ` Felix Seeger
2002-02-28 22:25       ` Bill Davidsen
2002-02-25 20:27 ` Christoph Hellwig
     [not found] <20020225200618.0FAE82069E@eos.telenet-ops.be>
2002-02-25 19:31 ` Marcelo Tosatti
2002-02-24  5:20   ` Daniel Phillips
2002-02-24  5:28     ` Daniel Phillips
2002-02-25 22:08   ` David S. Miller
2002-02-25 22:14     ` Thomas Duffy
2002-02-25 22:16       ` David S. Miller
2002-02-25 22:28         ` Lars Marowsky-Bree
2002-02-25 22:20     ` Rainer Ellinger
2002-02-25 22:19       ` David S. Miller
2002-02-25 23:01       ` Matthias Andree
2002-02-25 23:08         ` David S. Miller
2002-02-25 23:21           ` Jan Niehusmann
2002-02-25 23:32           ` Matthias Andree
2002-02-26  5:04             ` Bill Davidsen
2002-02-26  5:18               ` H. Peter Anvin
2002-02-26  9:09               ` Matthias Andree
2002-02-25 23:34           ` H. Peter Anvin
2002-02-25 23:55             ` David S. Miller
2002-02-26  1:09     ` David Relson
2002-02-26 13:25     ` Juan Quintela
2002-02-25 22:25   ` H. Peter Anvin
2002-02-25 22:50     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-02-25 18:37 Marcelo Tosatti
2002-02-25 18:57 ` Marcelo Tosatti
2002-02-25 20:41   ` Daniel Quinlan
2002-02-25 19:40     ` Marcelo Tosatti
2002-02-25 20:09 ` Hugh Dickins
2002-02-25 19:03   ` Marcelo Tosatti
2002-02-25 21:45 ` Florian Weimer

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=20020226174602.4f4b30bc.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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