From: Linus Torvalds <torvalds@linux-foundation.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Jake Edge <jake@lwn.net>,
"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 12:49:24 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906231246430.3240@localhost.localdomain> (raw)
In-Reply-To: <m3y6rilorn.fsf@intrepid.localdomain>
On Tue, 23 Jun 2009, Krzysztof Halasa wrote:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
> > 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.
>
> That's why i wrote: gain vs risk.
People really don't seem to be very good at the risk management part. They
see the gain, they don't think about the risk.
Note: not all maintainers are bad about this. But it tends to be my
biggest gripe after around -rc3 or so - people send stuff that is good,
but that really has no real reason not to be delayed.
And as long as people talk about this in terms of "bugs", it's a problem.
It would be much better to talk about it in terms of "Does this _really_
have to hit the next release? Honestly? Even though we're supposed to be
in the calming-down period?"
Linus
next prev parent reply other threads:[~2009-06-23 19:49 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
2009-06-23 19:43 ` Krzysztof Halasa
2009-06-23 19:49 ` Linus Torvalds [this message]
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=alpine.LFD.2.01.0906231246430.3240@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=jake@lwn.net \
--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=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