Thread (21 messages) 21 messages, 5 authors, 2009-06-13

Re: linux-next: origin tree build failure

From: Ingo Molnar <hidden>
Date: 2009-06-12 13:52:10
Also in: linux-next, lkml

* Benjamin Herrenschmidt [off-list ref] wrote:
On Fri, 2009-06-12 at 23:10 +1000, Benjamin Herrenschmidt wrote:
quoted
On Fri, 2009-06-12 at 14:53 +0200, Ingo Molnar wrote:
quoted
To some extent, here, the issue is on Linus side and it's up to him (Hey
Linus ! still listening ?) to maybe be more proactive at giving an ack
or nack so that we can get a chance to do that final pass of ironing out
the mechanical bugs before we hit the main tree.
Let me add a little bit more background to my reasoning here and why I
think having this integration testing step is so valuable...

It all boils down to bisection and having a bisectable tree.
I think you are way too concentrated on this particular incident, 
and you are generalizing it into something that is not so in 
practice.

Even in this particular case, there's just 3 other commit points in 
the Git tree between commit 8a1ca8c (the breakage on PowerPC) and 
e14112d (the fix). We'll have up to 10,000 commits.

I bisect on an almost daily basis, and i'm not seeing unreasonable 
problems.

	Ingo
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help