public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Rate of change
Date: Wed, 20 Oct 2004 15:34:16 +0100	[thread overview]
Message-ID: <20041020153416.E14627@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20041019213932.GA7383@havoc.gtf.org>; from jgarzik@pobox.com on Tue, Oct 19, 2004 at 05:39:32PM -0400

On Tue, Oct 19, 2004 at 05:39:32PM -0400, Jeff Garzik wrote:
> On Tue, Oct 19, 2004 at 05:37:59PM -0400, Dave Jones wrote:
> > On Tue, Oct 19, 2004 at 05:16:00PM -0400, Jeff Garzik wrote:
> >  > 
> >  > 850 changesets and 3383 revisions since 2.6.9 was released,
> >  > a little over 24 hours ago.
> >  > 
> >  > That's pretty impressive.
> > 
> > Given a lot of these are backlogs from folks being
> > conservative whilst we were in -rc, perhaps this is an
> > indication we need shorter -rc periods ?
> 
> 
> Actually, we need longer non-rc periods :)

Personally, I think both of you are right.  One major kernel release a
month seemed to be about the right rate.  Maybe a week and a half of
non-rc plus two and a half weeks of -rc would be the right kind of
balance?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-10-20 14:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 21:16 Rate of change Jeff Garzik
2004-10-19 21:31 ` Ben Dooks
2004-10-19 21:37 ` Dave Jones
2004-10-19 21:39   ` Jeff Garzik
2004-10-20 14:34     ` Russell King [this message]
2004-10-21 20:30     ` Jens Axboe
2004-10-22 10:28     ` Pavel Machek
2004-10-19 21:39 ` Måns Rullgård
2004-10-19 21:45 ` Matt Heler
2004-10-19 22:04   ` Jeff Garzik

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=20041020153416.E14627@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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