threads / discuss / 30789

git clone command

Subject: git clone command

## tl;dr

2 messages between Jun 13, 2012 and Jun 20, 2012.

replies: 1people: 2as markdown or json

Paa Kojo Konduah Amos· Jun 13, 2012, 05:09 UTC · lore

hello, i have been working with git for some time now... and i have just been hit with a serious problem in the middle of a major deployment of our project.

Problem: when i do a "git clone" on the server url without specifying 
the actual git repository..the command still pulls files of a previous 
clone rather than warning me the repository does not exist.

PLEASE what might be wrong...is there something like clean some cache.... i am really hot now!!!

Thanks.
Neal Kreitzinger· Jun 20, 2012, 20:49 UTC · re: Paa Kojo Konduah Amos · lore

Re: git clone command

On 6/13/2012 12:09 AM, Paa Kojo Konduah Amos wrote:
Show 11 quoted lines
> hello, i have been working with git for some time now... and i have just
> been hit with a serious problem in the middle of a major deployment of
> our project.
>
> Problem: when i do a "git clone" on the server url without specifying
> the actual git repository..the command still pulls files of a previous
> clone rather than warning me the repository does not exist.
>
> PLEASE what might be wrong...is there something like clean some
> cache.... i am really hot now!!!
>
git-clone manpage states:

<directory> The name of a new directory to clone into. The "humanish" part of the source repository is used if no directory is explicitly given (repo for /path/to/repo.git and foo for host.xz:foo/.git). Cloning into an existing directory is only allowed if the directory is empty.

I assume you're ending up with a new dir/worktree named after the humanish part of the repo-name in your url? mystery solved?

v/r, neal

← back to recent threads