[lkml]   [2001]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: drivers/char/sonypi.h broken
Alan Cox writes:
> > in 12 hours. I think this just highlights the need for BitKeeper or
> > equivalent, where automated regression testing (even a simple "does it
> > compile and link?") is performed, and if the test fails, it gets
> > bounced and doesn't even get to Linus.
> I do compile/link tests but not a million combinations of them. Its
> o(N!) remember..

Yes, and even if you were able to do so, there is still the problem of
testing against the version that Linus applies the patch to (which as
you said earlier, is a moving target). I guess one solution would be
to have the tool Linus uses (or should use:-) also do a test, and if
it fails, to bounce it. That would be done against Linus' working

However, that would reduce Linus' flexibility in applying a series of
patches which involves global API changes. Hm. Perhaps an option so
that Linus can accept a patch if he knows it's part of a global API

Another alternative, which has been raised before, is Linus' patch
queue is made public. As I understand it, Linus files pending patches
into a special folder, and then later feeds that folder, en-masse,
into patch(1), and a release/pre-patch is born. That patch queue could
be distributed using the mirror system. This would be a
generally useful thing, and with automated regression testing, reduces
the window for merge errors.


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:03    [W:0.055 / U:1.312 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site