From: Andrew Garber <andrew@andrewgarber.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Why can't I use git-bisect to find the first *good* commit?
Date: Mon, 28 Mar 2011 13:45:29 -0400 [thread overview]
Message-ID: <AANLkTimT+WN2F-BmQzQrAs3uizHig9cCXDUdc7nQ-vC5@mail.gmail.com> (raw)
In-Reply-To: <vpq62r3i1z4.fsf@bauges.imag.fr>
If branch bar is broken, do a bisect on branch bar. The fact that
branch foo works in inconsequential.
On Mon, Mar 28, 2011 at 1:33 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Andrew Garber <andrew@andrewgarber.com> writes:
>
>> On Mon, Mar 28, 2011 at 10:40 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
>>
>>> o--o--o--B
>>> /
>>> --o--o--o--o--G
>>>
>>> When I have this history and I mark B as bad and G as good, will I now
>>> find the first bad or the first good commit?
>>
>> That kind of situation shouldn't occur: IMO, bisect should only deal
>> with a single branch (the current branch).
>
> Why?
>
> It's not uncommon in real life to face the "it works in branch foo but
> not in branch bar, where did it break?" problem. And one expects a great
> tool such as Git to be able to answer it.
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
>
next prev parent reply other threads:[~2011-03-28 17:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 9:32 Why can't I use git-bisect to find the first *good* commit? Ævar Arnfjörð Bjarmason
2011-03-28 10:39 ` Andreas Ericsson
2011-03-28 12:22 ` code.sculptor
2011-03-28 12:58 ` Matthieu Moy
2011-03-28 12:39 ` Vincent van Ravesteijn
2011-03-28 14:04 ` Christian Couder
2011-03-28 14:29 ` Andrew Garber
2011-03-28 14:40 ` Johannes Sixt
2011-03-28 17:18 ` Andrew Garber
2011-03-28 17:33 ` Matthieu Moy
2011-03-28 17:45 ` Andrew Garber [this message]
2011-03-28 17:55 ` Matthieu Moy
2011-03-28 18:12 ` Andrew Garber
2011-03-28 18:23 ` Matthieu Moy
2011-03-28 18:57 ` demerphq
2011-03-28 19:12 ` Andrew Garber
2011-03-28 19:40 ` Matthieu Moy
2011-03-28 20:12 ` Andrew Garber
2011-03-28 20:25 ` Jeff King
2011-03-28 21:25 ` Jeff King
2011-03-28 20:37 ` Matthieu Moy
2011-03-29 10:54 ` Andreas Ericsson
2011-05-22 19:41 ` Michael Witten
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=AANLkTimT+WN2F-BmQzQrAs3uizHig9cCXDUdc7nQ-vC5@mail.gmail.com \
--to=andrew@andrewgarber.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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;
as well as URLs for NNTP newsgroup(s).