On Wed, Mar 4, 2015 at 6:44 PM, Junio C Hamano wrote:
> Troy Moure 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 --
Troy Moure 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.
On Tue, Mar 03, 2015 at 09:19:14AM -0500, Troy Moure wrote:
> I've found a case where git rev-list --bisect segfaults reproducibly
> (git version is 2.3.1). This is the commit topology (A2 is the first
> parent of M):
>
> I - A1 - A2
> \\
> - B1 -- M (HEAD)
Thanks for finding a si
Hi,
I've found a case where git rev-list --bisect segfaults reproducibly
(git version is 2.3.1). This is the commit topology (A2 is the first
parent of M):
I - A1 - A2
\\
- B1 -- M (HEAD)
And this is an example of a command that segfaults:
git rev-list --bisect --first-parent --p
4 matches
Mail list logo
