git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:48:01 +0800	[thread overview]
Message-ID: <be6fef0d0901290648g3e057255p2e69491edc3227e2@mail.gmail.com> (raw)
In-Reply-To: <20090129144036.GH21473@genesis.frugalware.org>

On Thu, Jan 29, 2009 at 10:40 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> [ Please don't top-post. ]

Oops.

> Ah, packed refs. :)
>
> See man git-pack-refs, git clone uses it to pack refs after a clone.
> They are still in the 'packed-refs' file.

Thanks, that does clears things up.


-- 
Cheers,
Ray Chuan

      reply	other threads:[~2009-01-29 14:49 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
2009-01-29 14:40     ` Miklos Vajna
2009-01-29 14:48       ` Tay Ray Chuan [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=be6fef0d0901290648g3e057255p2e69491edc3227e2@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).