[lkml]   [2002]   [May]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4 SRMMU bug revisited
On Tue, May 28, 2002 at 04:05:24AM -0700, David S. Miller wrote:
> From: Alan Cox <>
> 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 -
Linux 1394 -
Subversion -
Deqo -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:26    [W:0.065 / U:12.568 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site