From: Nanako Shiraishi <nanako3@lavabit.com>
To: Stephan Springl <springl-git@bfw-online.de>
Cc: git@vger.kernel.org
Subject: Re: BUG: git rev-list segfaults
Date: Thu, 16 Oct 2008 06:22:23 +0900 [thread overview]
Message-ID: <20081016062223.6117@nanako3.lavabit.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810152034040.7572@rosenkohl.springl.homeip.net>
Stephan Springl <springl-git@bfw-online.de> writes:
> git rev-list segfaults when crossing a merge commit when given
> --bisect-vars and --first-parent.
This is an old news, isn't it?
http://thread.gmane.org/gmane.comp.version-control.git/93416/focus=93420
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
prev parent reply other threads:[~2008-10-15 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 19:00 BUG: git rev-list segfaults Stephan Springl
2008-10-15 20:32 ` Avery Pennarun
2008-10-15 21:22 ` Nanako Shiraishi [this message]
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=20081016062223.6117@nanako3.lavabit.com \
--to=nanako3@lavabit.com \
--cc=git@vger.kernel.org \
--cc=springl-git@bfw-online.de \
/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