Re: git pull on Linux/ACPI release tree
- From
- Martin Langhoff <martin.langhoff-re5jqeeqqe8avxtiumwx3w@public.gmane.org>
- Date
- Jan 10, 2006, 06:38 UTC
- Message-ID
- <46a038f90601092238r3476556apf948bfe5247da484@mail.gmail.com>
- In-Reply-To
- <99D82C29-4F19-4DD3-A961-698C3FC0631D-ee4meeAH724@public.gmane.org>
On 1/10/06, Kyle Moffett <mrmacman_g4-ee4meeAH724@public.gmane.org> wrote:
> 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?
cheers,
martin - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html