From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Randy Dunlap <rddunlap@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
William Lee Irwin III <wli@holomorphy.com>,
Dave Jones <davej@redhat.com>
Subject: Re: Let's make a small change to the process
Date: Wed, 27 Oct 2004 16:05:17 +0100 [thread overview]
Message-ID: <1098889516.4302.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200410262220_MC3-1-8D36-77F@compuserve.com>
On Mer, 2004-10-27 at 03:17, Chuck Ebbert wrote:
> > If the goal of -ac is to only include those fixes, why can't we rename
> > it in something more "intuitive" for the final users ?
> > Do you see what I mean ?
>
> AFAICT -ac is not supposed to be a complete collection of bugfixes.
> 2.6.9-ac3 was certainly missing a lot of them (haven't seen -ac4 yet.)
The goal of -ac is to contain the stuff I personally consider important.
A lot of the smaller bugfixes individually are fine but a 'complete set
of bugfixes' turns into a large change set and then needs an entire
validation and release cycle of its own.
Each 2.6.10rc change I merged is on the basis of reward >> risk.
I don't care if its 2.6.9-ac or 2.6.9.4 personally but it's for Linus to
decide if he wants to do that and who he wants to make keeper of the
2.6.x.y tree if anyone.
Alan
next prev parent reply other threads:[~2004-10-27 16:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 2:17 Let's make a small change to the process Chuck Ebbert
2004-10-27 15:05 ` Alan Cox [this message]
2004-10-27 20:38 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 19:50 Chuck Ebbert
2004-10-26 10:44 My thoughts on the "new development model" Ed Tomlinson
2004-10-26 11:09 ` Massimo Cetra
2004-10-26 12:08 ` Paolo Ciarrocchi
2004-10-26 19:03 ` Mathieu Segaud
2004-10-26 20:16 ` Let's make a small change to the process Paolo Ciarrocchi
2004-10-26 20:22 ` William Lee Irwin III
2004-10-26 20:26 ` Paolo Ciarrocchi
2004-10-26 20:33 ` William Lee Irwin III
2004-10-26 20:36 ` Dave Jones
2004-10-26 20:44 ` Paolo Ciarrocchi
2004-10-27 0:51 ` Jan Knutar
2004-10-26 20:48 ` John Richard Moser
2004-10-26 21:00 ` Paolo Ciarrocchi
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=1098889516.4302.3.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=76306.1226@compuserve.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=rddunlap@osdl.org \
--cc=wli@holomorphy.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