From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Larry McVoy <lm@bitmover.com>,
torvalds@osdl.org, akpm@osdl.org
Subject: Re: BK kernel workflow
Date: Tue, 19 Oct 2004 23:33:40 +0200 [thread overview]
Message-ID: <4d8e3fd304101914332979f86a@mail.gmail.com> (raw)
In-Reply-To: <41753B99.5090003@pobox.com>
On Tue, 19 Oct 2004 12:06:49 -0400, Jeff Garzik <jgarzik@pobox.com> wrote:
> Although tangential to the problem, I thought LKML and BitMover (and
> maybe Andrew or Linus as well) might be interested in a general
> description of my workflow.
>
> For net drivers in the Linux kernel, there exists two patch queues,
> net-drivers-2.6 and netdev-2.6 (and corresponding 2.4 versions).
> net-drivers-2.6 could be described as the "upstream immediately" or "for
> Linus" queue, and netdev-2.6 could be described as the "testing" queue.
So you have two bk trees,
- patches good for mainstream
- patches good for -mm tree
It would be cool if all the maintainers could adopt your working method,
Andrew is already automatically pulling from a bunch of trees, why not
having Linusdoing the same too?
Something like:
linux-2.6.XX is released
- Linus pull from all the "patches good for mainstream" bk trees and
from the equivalent Andrew tree (that doesn't exist at the moment)
- Linus release the first -pre release
- Linus gets other patches according to the "old" method
- Linus releases the -pre/-rc
Is it just a stupid idea ?
--
Paolo
next prev parent reply other threads:[~2004-10-19 22:05 UTC|newest]
Thread overview: 161+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41752E53.8060103@pobox.com>
[not found] ` <20041019153126.GG18939@work.bitmover.com>
2004-10-19 16:06 ` BK kernel workflow Jeff Garzik
2004-10-19 21:33 ` Paolo Ciarrocchi [this message]
2004-10-19 21:38 ` Jeff Garzik
2004-10-19 21:54 ` Paolo Ciarrocchi
2004-10-19 22:11 ` Linus Torvalds
2004-10-20 7:35 ` Paolo Ciarrocchi
2004-10-23 16:12 ` Larry McVoy
2004-10-24 10:24 ` Paolo Ciarrocchi
2004-10-24 14:44 ` Larry McVoy
2004-10-24 16:44 ` Paolo Ciarrocchi
2004-10-24 23:32 ` Larry McVoy
2004-10-25 11:33 ` Matthias Urlichs
2004-10-25 11:46 ` Andrea Arcangeli
2004-10-25 12:29 ` Joe Perches
2004-10-25 13:39 ` Andrea Arcangeli
2004-10-25 15:14 ` Linus Torvalds
2004-10-25 15:43 ` Andrea Arcangeli
2004-10-25 16:10 ` Linus Torvalds
2004-10-25 17:22 ` Andrea Arcangeli
2004-10-25 20:04 ` Jeff Garzik
2004-10-26 2:19 ` Miles Bader
2004-10-25 16:20 ` Larry McVoy
2004-10-25 16:47 ` Andrea Arcangeli
2004-10-25 17:12 ` Larry McVoy
2004-10-25 17:34 ` Andrea Arcangeli
2004-10-25 17:18 ` Linus Torvalds
2004-10-25 17:37 ` Andrea Arcangeli
2004-10-26 0:06 ` Roman Zippel
2004-10-26 0:51 ` Linus Torvalds
2004-10-26 2:21 ` Miles Bader
2004-10-27 2:05 ` Roman Zippel
2004-10-27 3:00 ` Linus Torvalds
2004-10-27 4:18 ` Larry McVoy
2004-10-27 16:45 ` Matthias Urlichs
2004-10-27 18:12 ` Buddy Lucas
2004-10-27 20:56 ` Roman Zippel
2004-10-27 21:20 ` Linus Torvalds
2004-10-28 1:14 ` Roman Zippel
2004-10-28 1:34 ` Linus Torvalds
2004-10-27 21:45 ` Alan Cox
2004-10-31 19:50 ` Pavel Machek
2004-10-28 9:20 ` James Bruce
2004-10-28 11:39 ` Geert Uytterhoeven
2004-10-28 13:53 ` Larry McVoy
2004-10-28 14:06 ` Xavier Bestel
2004-10-28 15:10 ` Larry McVoy
2004-10-28 19:20 ` Alan Cox
2004-10-28 19:25 ` David Schwartz
2004-10-28 19:38 ` Kevin P. Fleming
2004-10-28 19:22 ` Alan Cox
2004-10-28 23:22 ` David Schwartz
2004-10-28 23:59 ` David S. Miller
2004-10-29 0:25 ` David Schwartz
2004-10-29 14:31 ` Scott Lockwood
2004-10-29 14:35 ` Xavier Bestel
2004-10-29 17:02 ` The requested ruling (Was: BK kernel workflow) Scott Lockwood
2004-10-30 2:08 ` David Schwartz
2004-10-28 19:59 ` BK kernel workflow Adrian Bunk
2004-10-28 21:35 ` Larry McVoy
2004-10-30 6:51 ` Adrian Bunk
2004-10-30 23:46 ` Larry McVoy
2004-10-30 23:05 ` Alan Cox
2004-10-31 17:47 ` Larry McVoy
2004-10-31 0:28 ` Robert Love
2004-10-31 1:11 ` Adrian Bunk
2004-10-29 17:19 ` Ramón Rey Vicente
2004-10-29 17:36 ` Larry McVoy
2004-10-29 18:06 ` Stephen Frost
2004-10-29 18:20 ` Larry McVoy
2004-10-29 18:08 ` Ramón Rey Vicente
2004-10-29 18:21 ` Larry McVoy
2004-10-29 18:33 ` Scott Lockwood
2004-10-29 18:55 ` Ramón Rey Vicente
2004-10-29 19:14 ` Scott Lockwood
2004-10-30 5:04 ` Kyle Moffett
2004-10-30 20:42 ` Scott Lockwood
2004-10-30 23:35 ` Larry McVoy
2004-10-31 0:20 ` David Schwartz
2004-10-31 2:37 ` Kyle Moffett
2004-10-31 3:34 ` Larry McVoy
2004-10-31 4:01 ` Kyle Moffett
2004-10-31 4:39 ` Larry McVoy
2004-10-31 2:44 ` Kyle Moffett
2004-10-29 19:39 ` Larry McVoy
2004-10-29 20:33 ` Stephen Frost
2004-10-29 23:38 ` Ramón Rey Vicente
2004-10-29 21:11 ` Adrian Bunk
2004-10-30 2:39 ` Larry McVoy
2004-10-30 2:02 ` Al Viro
2004-10-29 19:13 ` Ramón Rey Vicente
[not found] ` <45898.65.208.227.246.1099077395.squirrel@www.lrsehosting.com>
2004-10-29 19:26 ` Ramón Rey Vicente
2004-10-29 23:01 ` Tim Hockin
2004-10-29 20:32 ` Roman Zippel
2004-10-29 22:41 ` Larry McVoy
2004-10-30 11:38 ` Roman Zippel
2004-10-31 21:03 ` Pavel Machek
2004-10-31 21:14 ` Larry McVoy
2004-10-31 21:21 ` Pavel Machek
2004-10-31 21:35 ` Larry McVoy
2004-10-31 21:46 ` Pavel Machek
2004-10-31 23:44 ` Larry McVoy
2004-11-01 3:16 ` Kyle Moffett
2004-11-01 4:57 ` Larry McVoy
2004-11-01 8:39 ` Pavel Machek
2004-10-26 1:01 ` Larry McVoy
2004-10-27 2:30 ` Roman Zippel
2004-10-27 3:54 ` Larry McVoy
2004-10-27 20:58 ` Roman Zippel
2004-10-27 21:16 ` Joe Perches
2004-10-28 0:54 ` Larry McVoy
2004-10-28 1:49 ` Roman Zippel
2004-10-28 2:35 ` Linus Torvalds
2004-10-28 3:09 ` Larry McVoy
2004-10-28 21:03 ` Roman Zippel
2004-10-28 21:39 ` Eric Mudama
2004-10-28 22:45 ` Larry McVoy
2004-10-28 22:54 ` Roman Zippel
2004-10-29 8:09 ` Manu Abraham
2004-10-29 14:28 ` Scott Lockwood
2004-10-29 15:49 ` Roman Zippel
2004-10-29 16:41 ` David Schwartz
2004-10-29 17:20 ` Valdis.Kletnieks
2004-10-30 0:41 ` David Schwartz
2004-10-29 19:03 ` Chris Friesen
2004-10-29 20:00 ` Ryan Anderson
2004-10-30 0:41 ` David Schwartz
2004-10-31 20:47 ` Pavel Machek
2004-10-31 20:53 ` Larry McVoy
2004-10-31 22:07 ` Sam Ravnborg
2004-10-28 1:05 ` Theodore Ts'o
[not found] ` <mailman.1098759000.989.linux-kernel2news@redhat.com>
2004-10-30 3:55 ` Pete Zaitcev
2004-10-25 19:51 ` Matthias Urlichs
2004-10-26 0:58 ` Andrea Arcangeli
2004-10-26 2:23 ` Miles Bader
2004-10-25 18:18 ` Jon Smirl
2004-10-25 23:01 ` Larry McVoy
2004-10-26 1:28 ` Chris Wedgwood
2004-10-26 2:26 ` Jon Smirl
2004-10-26 6:57 ` Matthias Urlichs
2004-10-26 13:09 ` Giuseppe Bilotta
2004-10-24 17:44 ` Linus Torvalds
2004-10-24 17:48 ` Linus Torvalds
2004-10-24 18:39 ` Michael Buesch
2004-10-26 7:32 ` Matthias Urlichs
2004-10-24 22:33 ` Roman Zippel
2004-10-24 23:04 ` Linus Torvalds
2004-10-19 23:27 ` Greg KH
2004-10-25 13:01 ` Matthias Urlichs
2004-10-25 14:39 ` Paolo Ciarrocchi
2004-10-25 15:48 ` Jeff Garzik
2004-10-25 16:35 ` Matthias Urlichs
2004-10-25 22:05 ` Andrew Morton
2004-10-20 8:31 ` maximilian attems
2004-10-20 9:05 ` Jeff Garzik
2004-10-26 7:38 Chuck Ebbert
2004-10-26 14:23 ` Larry McVoy
2004-10-26 18:16 ` Ryan Anderson
2004-10-26 19:22 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2004-10-26 15:54 Chuck Ebbert
2004-10-26 20:47 ` Larry McVoy
[not found] <fa.gikv4k0.1tk6shk@ifi.uio.no>
[not found] ` <fa.d7r9f2v.1i6a6on@ifi.uio.no>
2004-10-30 20:54 ` walt
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=4d8e3fd304101914332979f86a@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.