From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: warren.l.dodge@tektronix.com
Cc: git@vger.kernel.org
Subject: Re: Error 128 Clone succeeded, but checkout failed
Date: Wed, 18 Jun 2014 23:55:39 +0000 [thread overview]
Message-ID: <20140618235539.GL368384@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <05c29ee7-8629-424e-b2db-de49db976e55@US-BV-EXH02-P.global.tektronix.net>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
On Wed, Jun 18, 2014 at 04:03:40PM -0700, warren.l.dodge@tektronix.com wrote:
> git.exe clone --progress -v L:\GIT_REPOSITORY L:\warrend\fail
>
> Cloning into L:\warrend\fail
> Done.
> Fatal: unable to read "Long hash key"
> Warning: clone succeeded, but checkout failed.
> You can inspect what was checked out with git status
> And retry the checkout with git checkout -f HEAD
What git version are you using?
Also, is this the exact (copy-and-pasted) message you're getting? There
are several similar messages starting with "unable to read", and knowing
the exact error message (including casing) is important in order to be
able to help you.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-18 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 23:03 Error 128 Clone succeeded, but checkout failed warren.l.dodge
2014-06-18 23:55 ` brian m. carlson [this message]
[not found] ` <C8DDA0C887F79C468978FDEF2DA46F9F0145B453@US-BV-EXM01-P.global.tektronix.net>
2014-06-19 0:24 ` brian m. carlson
2014-06-19 0:37 ` Dodge, Warren L
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=20140618235539.GL368384@vauxhall.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=warren.l.dodge@tektronix.com \
/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