From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 04 Mar 2015 23:44:19 GMT
Subject: Re: [BUG] Segfault with rev-list --bisect
Message-ID: <xmqq61ag72gc.fsf@gitster.dls.corp.google.com>
In-Reply-To: <CAMo-WNYNeShbbhNfG455o7krGfY7_9zVU3dMpJ7b4Smh_AiATg@mail.gmail.com>

Troy Moure <troy.moure@gmail.com> writes:

> git rev-list --bisect --first-parent --parents HEAD --not HEAD~1

Hmm, as "rev-list --bisect" is not end-user facing command (it is
purely an implementation detail for "git bisect") and we never call
it with --first-parent, I am not sure if it is worth labelling it as
a BUG.  Surely, the command can refuse to operate when it sees both
options given, but that would be a fairly low priority.

Of course, if you are planning to do "git bisect --first-parent", it
is one of the things that needs to be addressed, together with
counting the rounds and bisecting the linear set of commits on the
first-parent chain correctly.