linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	tshibata@ab.jp.nec.com
Subject: Re: [RFC] Documentation: add documentation for rc-series and merge window
Date: Mon, 15 Jun 2009 13:19:34 -0700	[thread overview]
Message-ID: <20090615201934.GA12685@kroah.com> (raw)
In-Reply-To: <1245096771-3966-1-git-send-email-lrodriguez@atheros.com>

On Mon, Jun 15, 2009 at 04:12:51PM -0400, Luis R. Rodriguez wrote:
> This is losely based on previous discussions on linux-kernel [1][2].
> 
> [1] http://marc.info/?l=linux-kernel&m=122048427801324&w=2
> [2] http://marc.info/?l=linux-netdev&m=122048757705315&w=2
> 
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> ---
> 
> I have run into issues when trying to explain this and policies
> for the rc-series, it seems there is no place that documents this
> clearly so here is an attempt based on some previous discussions.
> Not sure if I got it all correct, so feedback is welcomed. I do think
> clarifying this a little should help.
> 
> I was also not sure if Documentation/stable_kernel_rules.txt is the best
> splace for this as well, please let me know.

I don't think this is the best place for it, as the stable_* file is for
describing the rules for the 2.6.x.y releases, not the main 2.6.x
releases.

A new file perhaps?  Or an addition to the
Documentation/development-process/ book?

thanks,

greg k-h

  parent reply	other threads:[~2009-06-15 20:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 20:12 [RFC] Documentation: add documentation for rc-series and merge window Luis R. Rodriguez
2009-06-15 20:18 ` John W. Linville
2009-06-15 20:19 ` Greg KH [this message]
2009-06-15 21:47   ` Luis R. Rodriguez
2009-06-15 22:32     ` Greg KH
2009-06-16  0:41       ` Luis R. Rodriguez
2009-06-16  2:10         ` Luis R. Rodriguez
2009-06-16  3:20           ` Greg KH
2009-06-16  4:21             ` Luis R. Rodriguez
2009-06-16  4:39               ` Luis R. Rodriguez
2009-06-16  5:16               ` Greg KH
2009-06-16  9:34               ` Jouni Malinen
2009-06-16 16:19                 ` Stefan Richter
2009-06-16 18:17                 ` Luis R. Rodriguez
2009-06-19 15:00                   ` Pavel Machek
2009-06-19 17:10                     ` Luis R. Rodriguez
2009-06-19 17:41                       ` Justin Mattock
2009-06-19 22:19                       ` Pavel Machek
2009-06-19 22:49                         ` Krzysztof Halasa
2009-06-19 22:51                         ` Luis R. Rodriguez
2009-06-21  6:24                           ` Pavel Machek
2009-06-19 22:56                         ` Linus Torvalds
2009-06-21  0:47                           ` Luis R. Rodriguez
2009-06-15 20:31 ` Pavel Roskin
2009-06-15 20:40   ` Gábor Stefanik

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=20090615201934.GA12685@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tshibata@ab.jp.nec.com \
    /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;
as well as URLs for NNTP newsgroup(s).