From: Thomas Duffy <Thomas.Duffy.99@alumni.brown.edu>
To: "David S. Miller" <davem@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.18
Date: 25 Feb 2002 14:14:30 -0800 [thread overview]
Message-ID: <1014675271.12310.36.camel@tduffy-lnx.afara.com> (raw)
In-Reply-To: <20020225.140851.31656207.davem@redhat.com>
In-Reply-To: <20020225200618.0FAE82069E@eos.telenet-ops.be> <Pine.LNX.4.21.0202251631170.31542-100000@freak.distro.conectiva> <20020225.140851.31656207.davem@redhat.com>
On Mon, 2002-02-25 at 14:08, David S. Miller wrote:
>
> We can avoid this kind of mess in the future if the "-rc*" releases
> really are "release candidates" instead of "just another diff".
> Ie. they are done as patches _and_ tarballs, then the final can just
> be done with a "cp" command.
the problem with that is the top level Makefile still needs to be
changed. the last thing I want is to be running a 2.4.18-rc3 kernel and
have uname tell me it is 2.4.18.
-tduffy
next prev parent reply other threads:[~2002-02-25 22:15 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[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:14 ` Thomas Duffy [this message]
2002-02-25 22:25 ` H. Peter Anvin
2002-02-25 22:50 ` Alan Cox
2002-02-25 22:08 ` David S. Miller
2002-02-25 22:16 ` David S. Miller
2002-02-25 22:28 ` Lars Marowsky-Bree
2002-02-25 22:19 ` David S. Miller
2002-02-25 22:20 ` Rainer Ellinger
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 20:20 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 22:58 ` Bernd Eckenfels
2002-02-25 21:57 ` John Stoffel
2002-02-25 22:05 ` David S. Miller
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-25 20:27 ` Christoph Hellwig
2002-02-26 16:46 ` Stephan von Krawczynski
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
-- 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=1014675271.12310.36.camel@tduffy-lnx.afara.com \
--to=thomas.duffy.99@alumni.brown.edu \
--cc=davem@redhat.com \
--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
all inboxes | Powered by JetHome®