From: Junio C Hamano <gitster@pobox.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Richard Tibbitt <gitlist@lazyprune.com>, git@vger.kernel.org
Subject: Re: Failure cloning from a separate-git-dir repository
Date: Sun, 21 Aug 2011 11:51:43 -0700 [thread overview]
Message-ID: <7vippqy4w0.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACsJy8A4kvjn5Bgo6FtS+x4z=CRz8ctoDHh7D8XV3frOjDVfbw@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Sun, 21 Aug 2011 10:27:44 +0700")
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
> On Sun, Aug 21, 2011 at 1:56 AM, Richard Tibbitt <gitlist@lazyprune.com> wrote:
>> call git clone repo2git\.git clone2
>> fatal: repository 'repo2git\.git' does not exist
>>
>> I guess this must be a peculiarity of msysgit on windows.
>
> Yes. Try "call git clone repo2git/.git clone2" (forward slash). The
> forward slash is hard coded some places in git-clone. I just want to
> make sure you dont hit another problem.
As "fetch from bundle" (2e0afaf (Add git-bundle: move objects and
references by archive, 2007-02-22)) predates the "gitdir:" support
(b44ebb1 (Add platform-independent .git "symlink", 2008-02-20)) by a wide
margin, I wouldn't be surprised at all if the logic went "If the name can
be stat()ed and is a regular file, it must be a bundle. Otherwise it is a
local clone if it is a directory. All else ask the transport and see what
it says".
Why can't it be "git clone repo2git clone2" in the first place?
prev parent reply other threads:[~2011-08-21 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 17:47 Failure cloning from a separate-git-dir repository Richard Tibbitt
2011-08-20 18:25 ` Nguyen Thai Ngoc Duy
2011-08-20 18:56 ` Richard Tibbitt
2011-08-21 3:27 ` Nguyen Thai Ngoc Duy
2011-08-21 11:13 ` Richard Tibbitt
2011-08-21 18:51 ` Junio C Hamano [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=7vippqy4w0.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitlist@lazyprune.com \
--cc=pclouds@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