All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Randy Dunlap <rddunlap@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	William Lee Irwin III <wli@holomorphy.com>,
	Dave Jones <davej@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Let's make a small change to the process
Date: Tue, 26 Oct 2004 22:17:16 -0400	[thread overview]
Message-ID: <200410262220_MC3-1-8D36-77F@compuserve.com> (raw)

On Tue, 26 Oct 2004 at 22:44:21 +0200 Paolo Ciarrocchi wrote:
>
>> 2.6-ac seems to be filling this role right now.
>> 
>
> 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.)


--Chuck Ebbert  26-Oct-04  20:33:14

             reply	other threads:[~2004-10-27  2:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27  2:17 Chuck Ebbert [this message]
2004-10-27 15:05 ` Let's make a small change to the process Alan Cox
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=200410262220_MC3-1-8D36-77F@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.