All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jake Edge <jake@lwn.net>
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 12:11:52 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0906231210040.3240@localhost.localdomain> (raw)
In-Reply-To: <20090623130602.6cd6b713@chukar>



On Tue, 23 Jun 2009, Jake Edge wrote:

> On Tue, 23 Jun 2009 20:52:02 +0200 Krzysztof Halasa wrote:
> 
> > Perhaps it's just me :-) but I think we're trying to codify the rules
> > way too much. The general rules (merge window = new features etc) are
> > obviously ok but why do we need strict details like intrusive vs
> > non-intrusive etc? People should just use a common sense and good
> > judgement and, if in doubt in some particular case, ask. We are unable
> > to describe all situations in a single text file.
> 
> Me2 :)

Well, I do agree that documenting the rules and making them inflexible 
shouldn't be the primary goal.

But the fact is, "common sense" hasn't worked very well. I consistently 
get pull requests from maintainers that have well-meaning "fix bugs" in 
them, and that cause a lot of totally pointless churn.

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. 

			Linus

  reply	other threads:[~2009-06-23 19:12 UTC|newest]

Thread overview: 23+ 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  0:58   ` Li Zefan
2009-06-23 17:18 ` Jake Edge
2009-06-23 17:18   ` Jake Edge
2009-06-23 17:55   ` Luis R. Rodriguez
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 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:06       ` Jake Edge
2009-06-23 19:11       ` Linus Torvalds [this message]
2009-06-23 19:23         ` Jake Edge
2009-06-23 19:23           ` Jake Edge
2009-06-23 19:43         ` Krzysztof Halasa
2009-06-23 19:49           ` Linus Torvalds
2009-06-23 19:49             ` Linus Torvalds
2009-06-23 20:45         ` Luis R. Rodriguez
2009-06-23 20:45           ` Luis R. Rodriguez
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.0906231210040.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.