linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: "David S. Miller" <davem@redhat.com>
Cc: alan@lxorguk.ukuu.org.uk, szepe@pinerecords.com,
	colin@gibbs.dhs.org, linux-kernel@vger.kernel.org,
	tcallawa@redhat.com, sparclinux@vger.kernel.org,
	aurora-sparc-devel@linuxpower.org
Subject: Re: 2.4 SRMMU bug revisited
Date: Tue, 28 May 2002 08:10:44 -0400	[thread overview]
Message-ID: <20020528121044.GG30482@blimpo.internal.net> (raw)
In-Reply-To: <20020527213016.GB7155@beth.pinerecords.com> <20020527.204114.126236775.davem@redhat.com> <1022587118.4124.49.camel@irongate.swansea.linux.org.uk> <20020528.040524.117889173.davem@redhat.com>

On Tue, May 28, 2002 at 04:05:24AM -0700, David S. Miller wrote:
>    From: Alan Cox <alan@lxorguk.ukuu.org.uk>
>    Date: 28 May 2002 12:58:38 +0100
>    
>    Which is a concern since both Linus and Larry made it clear bitkeeper
>    would *NEVER* be required of contributors. Is there nothing generating
>    nightly tarballs off cron right now ?
>    
> As stated in a followup posting, that kind of thing is available.
> 
> I don't see why people fly off the handle on this.  It only matters if
> you need the tree as of 5 minutes ago bleeding edge type stuff.  If
> you can wait a few days, then just hang on for Marcelo's next
> prepatch.

Not trying to add fuel to the fire, but Marcelo's last prepatch was
almost 4 weeks ago (26 days). It makes life hard on even me, because
somehow a little tweak ends up changing the ieee1394 subsystem, and I
find myself resyncing over several pre-releases to get my patches in.

It sometimes seems that the bitkeeper repo is being used to pacify the
bleeding edge junkies (and rightfully so), but at the same time is
allowing the tree maintainers (not point fingers) to be more lax in
getting out frequent pre/full releases to the non-bitkeeper public (like
me). This inadvertently stalls productivity for the rest of us.

My problem getting things into the 2.5 tree seems more related to the
amount of work getting done in that tree as opposed to the lack of
releases, which is entirely acceptable. I'd prefer chasing frequent
releases to chasing invisible ones :)

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

  reply	other threads:[~2002-05-28 12:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27  9:24 2.4 SRMMU bug revisited Tomas Szepe
2002-05-27 10:17 ` David S. Miller
2002-05-27  6:20   ` Tomas Szepe
2002-05-27 10:40     ` David S. Miller
2002-05-27 11:19       ` [aurora-sparc-devel] " Tomas Szepe
2002-05-28 16:41         ` Denis Vlasenko
2002-05-28 12:11           ` David S. Miller
2002-05-27 18:46 ` Colin Gibbs
2002-05-27 19:34   ` Colin Gibbs
2002-05-28  1:12     ` Tomas Szepe
2002-05-27 21:30   ` Tomas Szepe
2002-05-28  3:41     ` David S. Miller
2002-05-28  5:40       ` Tomas Szepe
2002-05-28  8:39         ` David Woodhouse
2002-05-28 11:58       ` Alan Cox
2002-05-28 11:05         ` David S. Miller
2002-05-28 12:10           ` Ben Collins [this message]
2002-05-28 12:19             ` David S. Miller
2002-05-28  0:40   ` David S. Miller
2002-05-29 21:42   ` Tomas Szepe
     [not found] <mailman.1022584088.5530.linux-kernel2news@redhat.com>
2002-05-28 16:12 ` Pete Zaitcev

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=20020528121044.GG30482@blimpo.internal.net \
    --to=bcollins@debian.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=aurora-sparc-devel@linuxpower.org \
    --cc=colin@gibbs.dhs.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=szepe@pinerecords.com \
    --cc=tcallawa@redhat.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;
as well as URLs for NNTP newsgroup(s).