From: Dave Jones <davej@suse.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Rob Landley <landley@trommello.org>,
Bill Davidsen <davidsen@tmr.com>,
Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OKS] Kernel release management
Date: Sat, 6 Jul 2002 14:17:10 +0200 [thread overview]
Message-ID: <20020706141710.A8216@suse.de> (raw)
In-Reply-To: <20020704132120.C11601@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, Jul 04, 2002 at 01:21:20PM +0100
On Thu, Jul 04, 2002 at 01:21:20PM +0100, Russell King wrote:
> Think about who will do the stabilisation. Do you really think Alan or
> Marcelo will pick up 2.6 when it comes out? Or do you see someone else
> picking up 2.6?
Marcelo didn't seem against the idea, and as he's done a pretty good
job so far in 2.4, he seems to be the ideal guy for the job (time
permitting). At the time we get to 2.6.0, 2.4 should have slowed down
sufficiently that he'll be looking for something else to do.
> One of the fundamental questions that needs to be asked along side the
> "fork 2.7 with 2.6" problem is _who_ exactly is going to look after 2.6.
> Dave Jones? If Dave, who's going to do Daves job of making sure fixes
> get propagated between stable and development trees?
When we get to 2.6, I'll do 2.6-dj's until the important bits are all
pushed to $maintainer, and keep the leftovers until 2.7-dj.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-07-06 12:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 18:25 [OKS] Kernel release management Bill Davidsen
2002-07-01 18:56 ` Adrian Bunk
2002-07-01 19:24 ` Justin M. Forbes
2002-07-02 15:13 ` Bill Davidsen
2002-07-03 1:19 ` Rob Landley
2002-07-03 11:10 ` Matt Bernstein
2002-07-04 12:16 ` Russell King
2002-07-06 12:45 ` Theodore Ts'o
2002-07-07 19:37 ` Bernd Eckenfels
2002-07-04 12:02 ` Russell King
2002-07-04 13:33 ` Bill Davidsen
2002-07-04 14:32 ` Russell King
2002-07-03 15:34 ` Dave Jones
2002-07-03 14:24 ` Rob Landley
2002-07-04 2:18 ` jw schultz
2002-07-04 12:21 ` Russell King
2002-07-06 12:17 ` Dave Jones [this message]
2002-07-04 3:44 ` Bill Davidsen
[not found] <Pine.LNX.3.96.1020702110848.27954D-100000@gatekeeper.tmr.com.suse.lists.linux.kernel>
[not found] ` <200207030718.g637I0L145202@pimout2-int.prodigy.net.suse.lists.linux.kernel>
[not found] ` <20020704131654.B11601@flint.arm.linux.org.uk.suse.lists.linux.kernel>
2002-07-04 13:35 ` Andi Kleen
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=20020706141710.A8216@suse.de \
--to=davej@suse.de \
--cc=davidsen@tmr.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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