From: Mike Castle <dalgoda@ix.netcom.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.14-pre6
Date: Wed, 31 Oct 2001 11:55:14 -0800 [thread overview]
Message-ID: <20011031115514.F1767@thune.mrc-home.com> (raw)
In-Reply-To: <1004556431.11209.51.camel@mistress> <Pine.LNX.4.33.0110311126500.32727-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0110311126500.32727-100000@penguin.transmeta.com>
On Wed, Oct 31, 2001 at 11:38:44AM -0800, Linus Torvalds wrote:
> Then, 2.4.15 would be the point where I start 2.5.x, and where Alan gets
> to do whatever he wants to do with 2.4.x. Including, of course, just
> reverting all my and Andrea's VM changes ;)
There are a lot of patches applied to -ac that are not in the main line.
If many of those are applied to 2.4.16+, would they also be put into the
2.5.x line early in the process so that they will be fairly synced, plus
give you ample time to feel comfortable with their stability?
Especially patches that did not come directly from the maintainers.
mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
next prev parent reply other threads:[~2001-10-31 19:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 8:00 2.4.14-pre6 Linus Torvalds
2001-10-31 9:10 ` 2.4.14-pre6 Andrew Morton
2001-10-31 9:29 ` 2.4.14-pre6 Jens Axboe
2001-10-31 9:30 ` 2.4.14-pre6 bert hubert
2001-10-31 19:27 ` 2.4.14-pre6 Michael Peddemors
2001-10-31 19:38 ` 2.4.14-pre6 Linus Torvalds
2001-10-31 19:55 ` Mike Castle [this message]
2001-10-31 20:02 ` 2.4.14-pre6 Rik van Riel
2001-10-31 23:18 ` 2.4.14-pre6 Erik Andersen
2001-10-31 23:40 ` 2.4.14-pre6 Dax Kelson
2001-10-31 23:57 ` 2.4.14-pre6 Michael Peddemors
2001-10-31 19:52 ` 2.4.14-pre6 Philipp Matthias Hahn
2001-10-31 21:05 ` 2.4.14-pre6 H. Peter Anvin
2001-11-01 19:14 ` 2.4.14-pre6 Pozsar Balazs
2001-11-02 12:01 ` 2.4.14-pre6 Pavel Machek
2001-11-05 20:43 ` 2.4.14-pre6 Charles Cazabon
2001-11-05 20:49 ` 2.4.14-pre6 Linus Torvalds
2001-11-05 21:04 ` 2.4.14-pre6 Johannes Erdfelt
2001-11-05 21:08 ` 2.4.14-pre6 Wilson
2001-11-05 21:27 ` 2.4.14-pre6 Josh Fryman
2001-11-05 19:04 ` 2.4.14-pre6 Gérard Roudier
2001-11-02 16:48 ` 2.4.14-pre6 jogi
2001-11-03 12:47 ` 2.4.14-pre6 Mike Galbraith
2001-11-03 18:01 ` 2.4.14-pre6 Linus Torvalds
2001-11-03 19:07 ` 2.4.14-pre6 Mike Galbraith
2001-10-31 16:15 2.4.14-pre6 Linus Torvalds
2001-10-31 18:36 ` 2.4.14-pre6 Andrew Morton
2001-10-31 19:06 ` 2.4.14-pre6 Linus Torvalds
2001-11-01 10:20 ` 2.4.14-pre6 Neil Brown
2001-11-01 20:55 ` 2.4.14-pre6 Andrew Morton
2001-11-02 8:00 ` 2.4.14-pre6 Helge Hafting
2001-11-04 22:34 ` 2.4.14-pre6 Pavel Machek
2001-11-04 23:16 ` 2.4.14-pre6 Daniel Phillips
2001-11-01 21:28 ` 2.4.14-pre6 Chris Mason
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=20011031115514.F1767@thune.mrc-home.com \
--to=dalgoda@ix.netcom.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®