From: Johan Herland <johan@herland.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [PATCH 4/4] Teach "git clone" to pack refs
Date: Mon, 16 Jun 2008 00:03:06 +0200 [thread overview]
Message-ID: <200806160003.06300.johan@herland.net> (raw)
In-Reply-To: <20080615175613.GC6127@sigill.intra.peff.net>
On Sunday 15 June 2008, Jeff King wrote:
> On Sun, Jun 15, 2008 at 04:06:16PM +0200, Johan Herland wrote:
> > + pack_refs(PACK_REFS_ALL);
>
> I haven't looked carefully at the pack_refs code, but my understanding
> was that this would pack _all_ refs, including branches. Don't we
> generally try to leave branches unpacked, since they change a lot? IOW,
> shouldn't this just be "pack_refs(0)"?
Yes, for many repos it does not make much sense to pack branches. But in the
case where the repo has many inactive branches (I have repos with 1000
branches where at most 5-10 are still active), I'd much rather pack all
branches and then later "unpack" the active ones, than write all
those "loose" refs as separate files onto the filesystem (e.g. in CygWin
*shudder*). In any case, the user normally does not work actively on
hundreds of branches, so the overhead of "unpacking" active branches should
be fairly negligible in any case.
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2008-06-15 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 14:02 [PATCH 0/4] Teach "git clone" to pack refs Johan Herland
2008-06-15 14:04 ` [PATCH 1/4] Incorporate fetched packs in future object traversal Johan Herland
2008-06-15 14:05 ` [PATCH 2/4] Move pack_refs() and friends into libgit Johan Herland
2008-06-15 17:52 ` Jeff King
2008-06-15 21:27 ` [PATCH 2/4 v2] " Johan Herland
2008-06-15 14:05 ` [PATCH 3/4] Prepare testsuite for a "git clone" that packs refs Johan Herland
2008-06-15 17:54 ` Jeff King
2008-06-15 18:04 ` Jakub Narebski
2008-06-15 23:16 ` [PATCH 3/4 v2] " Johan Herland
2008-06-15 14:06 ` [PATCH 4/4] Teach "git clone" to pack refs Johan Herland
2008-06-15 17:56 ` Jeff King
2008-06-15 22:03 ` Johan Herland [this message]
2008-06-16 9:57 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2008-03-22 1:10 [RFC/PATCH 0/3] Teach builtin-clone " Johan Herland
2008-04-14 6:10 ` [RFC/PATCH 2/3] Prepare testsuite for a "git clone" that packs refs Daniel Barkalow
2008-04-14 8:00 ` Johan Herland
2008-04-14 8:04 ` [PATCH 4/4] Teach "git clone" to pack refs Johan Herland
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=200806160003.06300.johan@herland.net \
--to=johan@herland.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).