From: Junio C Hamano <gitster@pobox.com>
To: "Avery Pennarun" <apenwarr@gmail.com>
Cc: "Git ML" <git@vger.kernel.org>
Subject: Re: [bug] Segfault in git rev-list --first-parent --bisect
Date: Fri, 22 Aug 2008 21:51:43 -0700 [thread overview]
Message-ID: <7vhc9c49ls.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <32541b130808222020v146e015dm8a98a005ad3e76a7@mail.gmail.com> (Avery Pennarun's message of "Fri, 22 Aug 2008 23:20:31 -0400")
"Avery Pennarun" <apenwarr@gmail.com> writes:
> I've tried the following command sequence in git 1.5.6, 1.6.0,
> 1.6.0.8.ga578a, and 1.6.0.90.g436ed.
>
> $ git clone git://repo.or.cz/versaplex.git
> $ cd versaplex.git
> $ git rev-list --first-parent --bisect 5109c91 ^d798a2bfe094
> Segmentation fault
>
> Removing either the --first-parent or the --bisect makes the segfault go away.
Don't use them both then. I do not think --bisect pays any attention to
the usual revision traversal rules.
next prev parent reply other threads:[~2008-08-23 4:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 3:20 [bug] Segfault in git rev-list --first-parent --bisect Avery Pennarun
2008-08-23 4:51 ` Junio C Hamano [this message]
2008-08-23 5:20 ` Junio C Hamano
2008-08-23 5:31 ` Junio C Hamano
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=7vhc9c49ls.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).