From: Andreas Schwab <schwab@linux-m68k.org>
To: Thorkil Naur <naur@post11.tele.dk>
Cc: git@vger.kernel.org
Subject: Re: How do I investigate apparently random git clone reports of "error: File ... has bad hash"?
Date: Sun, 11 Sep 2011 22:13:10 +0200 [thread overview]
Message-ID: <m2mxeaet2h.fsf@igel.home> (raw)
In-Reply-To: <loom.20110911T210035-693@post.gmane.org> (Thorkil Naur's message of "Sun, 11 Sep 2011 19:03:03 +0000 (UTC)")
Thorkil Naur <naur@post11.tele.dk> writes:
> I have looked for git options (debug, verbosity) for increasing the amount of
> information reported, but have not managed to find anything that seemed useful
> in this situation.
Try adding -v -v when cloning. That also shows you that the server does
not support smart-http, which is suboptimal.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2011-09-11 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 19:03 How do I investigate apparently random git clone reports of "error: File ... has bad hash"? Thorkil Naur
2011-09-11 19:59 ` Andreas Schwab
2011-10-06 2:34 ` Thorkil Naur
2011-09-11 20:13 ` Andreas Schwab [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=m2mxeaet2h.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=naur@post11.tele.dk \
/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.