git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Error 128 Clone succeeded, but checkout failed

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jun 18, 2014, 23:55 UTC
Message-ID
<20140618235539.GL368384@vauxhall.crustytoothpaste.net>
In-Reply-To
<05c29ee7-8629-424e-b2db-de49db976e55@US-BV-EXH02-P.global.tektronix.net>
On Wed, Jun 18, 2014 at 04:03:40PM -0700, warren.l.dodge@tektronix.com wrote:
Show 8 quoted lines
> 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
Previous: warren.l.dodge@tektronix.comNext: brian m. carlson
Message 2 of 4 in “Error 128 Clone succeeded, but checkout failed”
  1. warren.l.dodge@tektronix.comJun 18, 2014
  2. brian m. carlsonJun 18, 2014
  3. brian m. carlsonJun 19, 2014
  4. Dodge, Warren LJun 19, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.