From: Jakub Narebski <jnareb@gmail.com>
To: Dave O <cxreg@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Segfault during merge
Date: Thu, 07 May 2009 03:17:54 -0700 (PDT) [thread overview]
Message-ID: <m3y6t9md2u.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.0905070102010.30999@narbuckle.genericorp.net>
Dave O <cxreg@pobox.com> writes:
> Hi, I've encountered a particular merge that causes a segfault, and was
> able to successfully bisect git to commit 36e3b5e. However, I'm unable
> to come up with a simple repro that doesn't involve the source tree that
> I found it on, which unfortunately I'm not able to share.
[...]
> Please let me know how I can further help debug this issue, or possibly
> come up with a repro that will help someone else debug it. Thanks!
Couldn't you use repository anonymizing tool (which replaces all
content, but preserves shape of history) which was published as
example some time ago on git mailing list? Unfortunately I don't
have it bookmarked, so you would have to search for it yourself.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-05-07 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 8:28 Segfault during merge Dave O
2009-05-07 9:48 ` Johannes Schindelin
2009-05-08 4:37 ` Dave O
2009-05-08 20:30 ` [PATCH] Fix segfault in merge-recursive Johannes Schindelin
2009-05-08 21:41 ` Dave O
2009-05-08 22:14 ` Johannes Schindelin
2009-05-08 23:54 ` Dave O
2009-05-09 5:30 ` [PATCH] Don't update index while recursing (was Re: Segfault during merge) Dave O
2009-05-09 7:57 ` Johannes Schindelin
2009-05-09 16:54 ` [PATCH] Fix segfault in merge-recursive Junio C Hamano
2009-05-08 23:36 ` Junio C Hamano
2009-05-09 7:48 ` Johannes Schindelin
2009-05-07 10:17 ` Jakub Narebski [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=m3y6t9md2u.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=cxreg@pobox.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).