From: Johan Herland <johan@herland.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, "Kristian Høgsberg" <krh@redhat.com>
Subject: Re: [RFC] git-clone should create packed refs
Date: Fri, 15 Feb 2008 02:13:38 +0100 [thread overview]
Message-ID: <200802150213.38532.johan@herland.net> (raw)
In-Reply-To: <alpine.LSU.1.00.0802150051320.30505@racer.site>
On Friday 15 February 2008, Johannes Schindelin wrote:
> Hi,
>
> On Fri, 15 Feb 2008, Johan Herland wrote:
>
> > when git-clone is cloning repos with thousands of refs, it makes sense
> > to create a packed-refs file directly in the clone, instead of having to
> > run "git pack-refs" (or "git gc") afterwards to (re)pack the refs.
>
> Sure, and it's easy, too. The format of the packed-refs file is exactly
> the same as the output of "git ls-remote <origin>".
As I said in my first email: similar, but not identical.
Contrast:
$ git ls-remote origin
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd HEAD
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd refs/heads/another_branch
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd refs/heads/master
d6f7eacba9f07aa382a113e129866266c8d60642 refs/tags/complex_tag
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd refs/tags/complex_tag^{}
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd refs/tags/simple_tag
$ cat .git/packed-refs
# pack-refs with: peeled
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd refs/heads/master
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd refs/remotes/origin/another_branch
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd refs/remotes/origin/master
d6f7eacba9f07aa382a113e129866266c8d60642 refs/tags/complex_tag
^ec09f49905e94f3bbf04bf3521f1fc59b1345cbd
ec09f49905e94f3bbf04bf3521f1fc59b1345cbd refs/tags/simple_tag
$
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
prev parent reply other threads:[~2008-02-15 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 0:33 [RFC] git-clone should create packed refs Johan Herland
2008-02-15 0:53 ` Johannes Schindelin
2008-02-15 1:13 ` Johan Herland [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=200802150213.38532.johan@herland.net \
--to=johan@herland.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=krh@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.