From: Jakub Narebski <jnareb@gmail.com>
To: David Gilman <davidgilman1@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Reproducible crash in git merge
Date: Sun, 27 Mar 2011 10:23:13 -0700 (PDT) [thread overview]
Message-ID: <m3pqpcv5ph.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimxHn_fwMKh9cbp9i5LkShUi=HK44nv2KJ7ENaQ@mail.gmail.com>
David Gilman <davidgilman1@gmail.com> writes:
> I can get git merge to crash during a git pull. I'm using git
> 1.7.3.2. The repo (afaict) is fine and had worked previously.
"git fsck --all" doesn't show any _errors_, doesn't it?
> Unfortunately I can't share the repo itself because of its contents.
Does anyone remember the script that can be used to anonymize contents
of repository that cannot be made public for debugging purposes?
Unfortunately I didn't save this email (on git mailing list), nor do
I remember enough from email to find it on one of git mailing list
archives...
It would be good if it made it into 'contrib/' area, isn't it?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-03-27 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 16:54 Reproducible crash in git merge David Gilman
2011-03-27 17:23 ` Jakub Narebski [this message]
2011-03-27 18:01 ` Junio C Hamano
2011-03-29 18:40 ` Jakub Narebski
2011-03-27 20:24 ` David Gilman
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=m3pqpcv5ph.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=davidgilman1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.