From: Tay Ray Chuan <rctay89@gmail.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: git clone --bare doesn't create refs/heads/*?
Date: Thu, 29 Jan 2009 22:36:26 +0800 [thread overview]
Message-ID: <be6fef0d0901290636m5b472499mdf614841a06ec978@mail.gmail.com> (raw)
In-Reply-To: <20090129142657.GG21473@genesis.frugalware.org>
Hmm, no, --mirror adds extra remote tracking information.
Quoting the git-clone man page:
"...the branch heads at the remote are copied directly..."
which is to say, git clone --bare isn't doing what it's supposed to do.
that said, i'm not too sure about this, hence this thread.
On Thu, Jan 29, 2009 at 10:26 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Thu, Jan 29, 2009 at 10:06:39PM +0800, Tay Ray Chuan <rctay89@gmail.com> wrote:
>> afaik, a bare repository is just a copy of the .git folder of the
>> cloned repository. why isn't any of its branches copied too?
>
> Maybe you're searching for git clone --mirror and not git clone --bare?
>
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2009-01-29 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 14:06 git clone --bare doesn't create refs/heads/*? Tay Ray Chuan
2009-01-29 14:26 ` Miklos Vajna
2009-01-29 14:36 ` Tay Ray Chuan [this message]
2009-01-29 14:40 ` Miklos Vajna
2009-01-29 14:48 ` Tay Ray Chuan
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=be6fef0d0901290636m5b472499mdf614841a06ec978@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.org \
/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).