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 14:12:06 -0400 [thread overview]
Message-ID: <AANLkTinuH4Ut+jtdqRfFrNeXA6JmBK2i0ddCcz4vV6JC@mail.gmail.com> (raw)
In-Reply-To: <vpqr59r6sg5.fsf@bauges.imag.fr>
On Mon, Mar 28, 2011 at 1:55 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Then which commit do you specify as "good"?
Any ancestral commit *on the same branch* which is know to be working.
Isn't the whole point of git bisect is to do binary search through
time? It only makes sense to me to use it on a single branch at a
time. Perhaps you could give a concrete example of where you could use
it for multiple branches simultaneously?
next prev parent reply other threads:[~2011-03-28 18:12 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
2011-03-28 17:55 ` Matthieu Moy
2011-03-28 18:12 ` Andrew Garber [this message]
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=AANLkTinuH4Ut+jtdqRfFrNeXA6JmBK2i0ddCcz4vV6JC@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).