From: Martin Langhoff <martin.langhoff@gmail.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Luben Tuikov <ltuikov@yahoo.com>,
"Brown, Len" <len.brown@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@osdl.org>,
"David S. Miller" <davem@davemloft.net>,
linux-acpi@vger.kernel.org,
LKML Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git pull on Linux/ACPI release tree
Date: Tue, 10 Jan 2006 19:38:07 +1300 [thread overview]
Message-ID: <46a038f90601092238r3476556apf948bfe5247da484@mail.gmail.com> (raw)
In-Reply-To: <99D82C29-4F19-4DD3-A961-698C3FC0631D@mac.com>
On 1/10/06, Kyle Moffett <mrmacman_g4@mac.com> 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
next prev parent reply other threads:[~2006-01-10 6:38 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 8:05 Brown, Len
2006-01-09 16:47 ` Linus Torvalds
2006-01-09 16:57 ` Linus Torvalds
2006-01-09 22:51 ` Luben Tuikov
2006-01-09 23:07 ` Linus Torvalds
2006-01-09 23:34 ` Martin Langhoff
2006-01-10 2:50 ` Linus Torvalds
2006-01-10 6:33 ` Kyle Moffett
2006-01-10 6:38 ` Martin Langhoff [this message]
2006-01-10 18:05 ` Kyle Moffett
2006-01-10 18:27 ` Linus Torvalds
2006-01-10 18:45 ` Johannes Schindelin
2006-01-10 19:01 ` Linus Torvalds
2006-01-10 19:28 ` Linus Torvalds
2006-01-13 23:35 ` Matthias Urlichs
2006-01-11 3:32 ` Luben Tuikov
2006-01-09 20:06 ` Junio C Hamano
2006-01-10 15:31 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 7:34 Brown, Len
2006-01-09 10:11 ` Martin Langhoff
2006-01-09 12:31 ` Johannes Schindelin
2006-01-09 6:27 Brown, Len
2006-01-09 6:13 Brown, Len
2006-01-09 5:55 linux
2006-01-09 5:53 Brown, Len
2006-01-09 6:08 ` Martin Langhoff
2006-01-09 6:13 ` Linus Torvalds
2006-01-09 6:46 ` Junio C Hamano
2006-01-08 18:28 Brown, Len
2006-01-08 19:19 ` Martin Langhoff
2006-01-08 19:33 ` Junio C Hamano
2006-01-08 19:57 ` Linus Torvalds
2006-01-08 20:50 ` Tony Luck
2006-01-08 19:56 ` Linus Torvalds
2006-01-08 20:35 ` David S. Miller
2006-01-08 21:20 ` Luben Tuikov
2006-01-09 1:13 ` Linus Torvalds
2006-01-08 19:41 ` Linus Torvalds
2006-01-08 23:06 ` Adrian Bunk
2006-01-08 23:53 ` Willy Tarreau
2006-01-09 3:26 ` Linus Torvalds
2006-01-09 4:34 ` Martin Langhoff
2006-01-10 20:19 ` Adrian Bunk
2006-01-10 20:31 ` Linus Torvalds
2006-01-10 20:33 ` Martin Langhoff
2006-01-12 1:37 ` Greg KH
2006-01-12 16:10 ` Catalin Marinas
2006-01-13 14:50 ` Adrian Bunk
2006-01-08 7:47 Brown, Len
2006-01-08 8:16 ` David S. Miller
2006-01-08 8:16 ` Catalin Marinas
2006-01-08 19:10 ` Linus Torvalds
2006-01-09 0:48 ` Al Viro
2006-01-09 3:50 ` Linus Torvalds
2005-12-01 8:05 Len Brown
2005-12-06 8:17 ` Len Brown
2005-12-23 5:42 ` Len Brown
2006-01-07 15:54 ` Len Brown
2006-01-07 18:22 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46a038f90601092238r3476556apf948bfe5247da484@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltuikov@yahoo.com \
--cc=mrmacman_g4@mac.com \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®