lkml.org 
[lkml]   [2004]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: BK kernel workflow
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.255 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site