Thanks to Sverre Rabbelier who reminded me to do a 'git init' to get rid of that
"Not a git repository' error. So I did:
$ mkdir sss3
$ cd sss3
$ git init
$ git remote add origin git@xxxxxxxxxx:XXX/YYY.git
$ 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
$ git checkout -b master origin/master
Checking out files: 43%
tagging': Invalid argumenttory at 'public/images/tagging
I'm still getting the same print over error messages. Thanks for any help that
might help me to resolve this perplexing problem.
Hoca
----- Original Message ----
From: Hocapito Cheteamo <hocapitocheteamo@xxxxxxxxx>
To: Johannes Sixt <j.sixt@xxxxxxxxxxxxx>
Cc: git@xxxxxxxxxxxxxxx
Sent: Wed, October 6, 2010 12:50:13 AM
Subject: Re: Error on git clone
Yes, this is with "Git for Windows" (a Git Bash Shell window).
So I did what you suggested:
mkdir sss3
cd sss3
git remote add origin git@xxxxxxxxxx:XXX/YYY.git
Then an error occurs:
fatal: Not a git repository (or any of the parent directories): .git
Any thoughts?
Thanks.
Hoca
----- Original Message ----
From: Johannes Sixt <j.sixt@xxxxxxxxxxxxx>
To: Hocapito Cheteamo <hocapitocheteamo@xxxxxxxxx>
Cc: git@xxxxxxxxxxxxxxx
Sent: Wed, October 6, 2010 12:22:28 AM
Subject: Re: Error on git clone
Am 10/6/2010 10:13, schrieb Hocapito Cheteamo:
> I could consistently reproduce the problem. The command that I used is:
> git clone -v git@xxxxxxxxxx:XXX/YYY.git sss
> where XXX & YYY are replaced with the actual data.
Just to make sure: This is with "Git for Windows", not Cygwin's git?
Do the clone in separate the steps:
mkdir sss
cd sss
git remote add origin git@xxxxxxxxxx:XXX/YYY.git
git fetch
git checkout -b master origin/master
Do you see any errors?
-- Hannes
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html