From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Paa Kojo Konduah Amos <pkkamos@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git clone command
Date: Wed, 20 Jun 2012 15:49:33 -0500 [thread overview]
Message-ID: <4FE2375D.5010409@gmail.com> (raw)
In-Reply-To: <4FD82090.8010509@gmail.com>
On 6/13/2012 12:09 AM, Paa Kojo Konduah Amos wrote:
> 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
prev parent reply other threads:[~2012-06-20 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 5:09 git clone command Paa Kojo Konduah Amos
2012-06-20 20:49 ` Neal Kreitzinger [this message]
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=4FE2375D.5010409@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=git@vger.kernel.org \
--cc=pkkamos@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).