Re: [RFC] Documentation: add documentation for rc-series and mergewindow
From: Luis R. Rodriguez
Date: Mon Jun 15 2009 - 20:41:35 EST
On Mon, Jun 15, 2009 at 03:32:06PM -0700, Greg KH wrote:
> On Mon, Jun 15, 2009 at 05:47:35PM -0400, Luis R. Rodriguez wrote:
> > From: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx>
> > Subject: [PATCH] Documentation: add documentation summary for rc-series and merge window
> > This is losely based on previous discussions on linux-kernel .
> > Lets also refer people reading the stable rules to
> > Documentation/development-process/.
> >  http://marc.info/?l=linux-kernel&m=122048427801324&w=2
> >  http://marc.info/?l=linux-netdev&m=122048757705315&w=2
> > Signed-off-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx>
> > ---
> > Documentation/development-process/2.Process | 66 +++++++++++++++++++++++++++
> > Documentation/stable_kernel_rules.txt | 5 ++
> > 2 files changed, 71 insertions(+), 0 deletions(-)
> > diff --git a/Documentation/development-process/2.Process b/Documentation/development-process/2.Process
> > index d750321..e023db6 100644
> > --- a/Documentation/development-process/2.Process
> > +++ b/Documentation/development-process/2.Process
> You should cc: the author of this document, when modifying it.
> > @@ -7,6 +7,72 @@ course of one year, the kernel has since had to evolve a number of
> > processes to keep development happening smoothly. A solid understanding of
> > how the process works is required in order to be an effective part of it.
> > +2.0 SUMMARY
> > +
> > +This section provides a brief summary of the new kernel release rules.
> > +
> > +2.0.0 NEW KERNEL RELEASE RULES
> "New"? We've been doing this for many many years now, what is "new"
> about it?
New as in the next kernel release, sorry. Didn't mean as in "this is a
> And why are you starting a series with "0"? Just to keep from having to
> modify all of the other numbers? None of the other files in this
> directory start at 0...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/