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

Re: Error on git clone

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Oct 6, 2010, 10:51 UTC
Message-ID
<4CAC54CB.5020208@viscovery.net>
In-Reply-To
<571212.33119.qm@web114615.mail.gq1.yahoo.com>
Am 10/6/2010 12:34, schrieb Hocapito Cheteamo:
Show 8 quoted lines
> $ git fetch
> Enter passphrase for key 'C:\.....\privateKey':
> remote: Counting objects: 478, done.
> remote: Compressing objects: 100% (303/303), done.
> Receiving objects: 100% (478/478), 96.57 MiB | 166 KiB/s, done.
> Resolving deltas: 100% (21/21), done.
> From github.com:XXX/YYY
>  * [new branch]      master     -> origin/master

Ok, download works as expected. You don't have to repeat these steps anymore. Keep a copy of sss3\.git around so that you can go back to this state when necessary.

> $ git checkout -b master origin/master
> Checking out files: 43%
> tagging': Invalid argumenttory at 'public/images/tagging
The error message is this one:
cannot create directory at '%s'
Do you have a file/directory with a CR in it? When you run this:
 git -p ls-tree -r origin/master
and look for public/images, do you see this:
"public/images/tagging\rtagging"

(including the double-quotes)? If so, ask your upstream to fix the repository; you can't checkout the data as is on Windows.

Alternatively, you could use a sparse checkout that excludes the questionable file. Read "Sparse checkout" in http://www.kernel.org/pub/software/scm/git/docs/git-read-tree.html

-- Hannes
Previous: Hocapito CheteamoNext: Hocapito Cheteamo
Message 2 of 3 in “Re: Error on git clone”
  1. Hocapito CheteamoOct 6, 2010
  2. Johannes SixtOct 6, 2010
  3. Hocapito CheteamoOct 6, 2010

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.