Re: git pull on Linux/ACPI release tree

On Jan 10, 2006, at 01:38, Martin Langhoff wrote:

On 1/10/06, Kyle Moffett [off-list ref] wrote:

quoted

If they all work, then we know precisely that it's the  
interactions between them, which also makes debugging a lot easier.

The more complex your tree structure is, the more the interactions  
are likely to be part of the problem. Is git-bisect not useful in  
this scenario?

IIRC git-bisect just does an outright linearization of the whole tree  
anyways, which makes git-bisect work everywhere, even in the presence  
of difficult cross-merges.  On the other hand, if you are git- 
bisecting ACPI changes (perhaps due to some ACPI breakage), and ACPI  
has 10 pulls from mainline, you _also_ have to wade through the  
bisection of any other changes that occurred in mainline, even if  
they're totally irrelevant.  This is why it's useful to only pull  
mainline into your tree (EX: ACPI) when you functionally depend on  
changes there (as Linus so eloquently expounded upon).

Cheers,
Kyle Moffett

--
Q: Why do programmers confuse Halloween and Christmas?
A: Because OCT 31 == DEC 25.