From: Max Horn <max@quendi.de>
To: git@vger.kernel.org
Subject: [PATCH] fast-export: report SHA-1 instead of gibberish when marks
Date: Tue, 12 Jun 2012 15:45:15 +0200 [thread overview]
Message-ID: <1339508716-51880-1-git-send-email-max@quendi.de> (raw)
This patch should be a fairly obvious bug fix. Just yesterday I run into
it, when testing some buggy code that lead to this error message being
triggered; the results was lots of unreadable binary gibberish
filling my terminal.
While I did not author this commit, I asked its author for (and received)
permission to submit it here. Hopefully this can be included in mainline git
(this would ease work on git-remote-hg a bit ;).
next reply other threads:[~2012-06-12 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 13:45 Max Horn [this message]
2012-06-12 13:45 ` [PATCH] fast-export: report SHA-1 instead of gibberish when marks exist already Max Horn
2012-06-12 14:26 ` 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=1339508716-51880-1-git-send-email-max@quendi.de \
--to=max@quendi.de \
--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).