From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pavel Machek <pavel@ucw.cz>, Jouni Malinen <j@w1.fi>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
Greg KH <greg@kroah.com>, "corbet@lwn.net" <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"tshibata@ab.jp.nec.com" <tshibata@ab.jp.nec.com>,
Tomas Winkler <tomasw@gmail.com>
Subject: Re: [RFC] Documentation: add documentation for rc-series and merge window
Date: Sat, 20 Jun 2009 17:47:43 -0700 [thread overview]
Message-ID: <43e72e890906201747qb409fa7ue1bc84272417e03@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0906191555390.16802@localhost.localdomain>
On Fri, Jun 19, 2009 at 3:56 PM, Linus
Torvalds<torvalds@linux-foundation.org> wrote:
>
>
> On Sat, 20 Jun 2009, Pavel Machek wrote:
>>
>> Non-intrusive bugfixes _are_ welcome after -rc1.
>
> After -rc1, yes.
>
> After something like -rc5? No.
>
> They had better be _really_ important things, and _really_ obvious and
> non-intrusive. Not just "any bug".
For the sake of documentation and to help developers better understand
this it would be nice if we could be a little more clear here. I can
think of patches which may not be obvious but yet very important, for
example. Can we simply document that the patches must be important,
non-intrusive, and must have a very clear commit log entry of what it
is fixing. Judgment for the degree of importance of the patch can be
left up to the subsystem maintainer.
Is it reasonable to document this as I describe above?
Luis
next prev parent reply other threads:[~2009-06-21 0:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 20:12 Luis R. Rodriguez
2009-06-15 20:18 ` John W. Linville
2009-06-15 20:19 ` Greg KH
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-20 1:35 ` netlink interface change and crash while feeing associated sk_buff Vinay Venkataraghavan
2009-06-19 22:19 ` [RFC] Documentation: add documentation for rc-series and merge window 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 [this message]
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=43e72e890906201747qb409fa7ue1bc84272417e03@mail.gmail.com \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=j@w1.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tomasw@gmail.com \
--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
Powered by JetHome