From: Johannes Sixt <j.sixt@viscovery.net>
To: Hocapito Cheteamo <hocapitocheteamo@yahoo.com>
Cc: git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: Error on git clone
Date: Wed, 06 Oct 2010 12:51:55 +0200 [thread overview]
Message-ID: <4CAC54CB.5020208@viscovery.net> (raw)
In-Reply-To: <571212.33119.qm@web114615.mail.gq1.yahoo.com>
Am 10/6/2010 12:34, schrieb Hocapito Cheteamo:
> $ 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
next prev parent reply other threads:[~2010-10-06 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 10:34 Error on git clone Hocapito Cheteamo
2010-10-06 10:51 ` Johannes Sixt [this message]
2010-10-06 18:22 ` Hocapito Cheteamo
-- strict thread matches above, loose matches on Subject: below --
2010-10-06 4:20 Hocapito Cheteamo
2010-10-06 6:35 ` Johannes Sixt
2010-10-06 8:13 ` Hocapito Cheteamo
2010-10-06 8:22 ` Johannes Sixt
2010-10-06 8:50 ` Hocapito Cheteamo
2010-10-06 8:55 ` Sverre Rabbelier
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=4CAC54CB.5020208@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=hocapitocheteamo@yahoo.com \
--cc=srabbelier@gmail.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;
as well as URLs for NNTP newsgroup(s).