From: Jake Edge <jake@lwn.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Pavel Machek <pavel@ucw.cz>, 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>
Subject: Re: [PATCH v3.1415] Documentation: add documentation summary for rc-series and merge window
Date: Tue, 23 Jun 2009 13:23:16 -0600 [thread overview]
Message-ID: <20090623132316.28a4a348@chukar> (raw)
In-Reply-To: <alpine.LFD.2.01.0906231210040.3240@localhost.localdomain>
On Tue, 23 Jun 2009 12:11:52 -0700 (PDT) Linus Torvalds wrote:
> In fact, this whole discussion has shown one thing: people still
> think that "bug fix" somehow automatically means that it's
> appropriate after the merge window. That's simply not so.
Makes sense. It certainly is counter-intuitive sometimes, though.
Just to clarify, there would seem to be one other category of bugs that
is reasonable post-merge-window: those introduced by new features (or
bug fixes) that were added during the merge window (i.e. something
found in testing the new code during the -rc cycle). Those don't
necessarily have to be security/oops problems and, for the most part,
can't be regressions (at least for new features). Or should those
wait, by and large, for the next merge window?
jake
--
Jake Edge - LWN - jake@lwn.net - http://lwn.net
next prev parent reply other threads:[~2009-06-23 19:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 22:22 [PATCH v3.1415] Documentation: add documentation summary for rc-series and merge window Luis R. Rodriguez
2009-06-23 0:58 ` Li Zefan
2009-06-23 17:18 ` Jake Edge
2009-06-23 17:55 ` Luis R. Rodriguez
2009-06-23 18:37 ` Greg KH
2009-06-23 19:02 ` Jake Edge
2009-06-23 18:52 ` Krzysztof Halasa
2009-06-23 19:04 ` Linus Torvalds
2009-06-23 19:06 ` Jake Edge
2009-06-23 19:11 ` Linus Torvalds
2009-06-23 19:23 ` Jake Edge [this message]
2009-06-23 19:43 ` Krzysztof Halasa
2009-06-23 19:49 ` Linus Torvalds
2009-06-23 20:45 ` Luis R. Rodriguez
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=20090623132316.28a4a348@chukar \
--to=jake@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--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).