| commit | 3e8aded20329bef35470eb469281f6b275d19dea | |
| author | Johan Herland <johan@herland.net> | |
| Sun, 15 Jun 2008 14:06:16 +0000 (15 16:06 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 19 Jun 2008 22:53:13 +0000 (19 15:53 -0700) | ||
| tree | cbb3d3d54236053acfba16d3ed1f9d16cf1d7a49 | treesnapshot (tar.gz zip) |
| parent | d0d12b476822bb8686ee883bd44b799563069a48 | commitdiff |
Teach "git clone" to pack refs
In repos with many refs, it is unlikely that most refs will ever change.
This fact is already exploited by "git gc" by executing "git pack-refs"
to consolidate all refs into a single file.
When cloning a repo with many refs, it does not make sense to create the
loose refs in the first place, just to have the next "git gc" consolidate
them into one file. Instead, make "git clone" create the packed refs file
immediately, and forego the loose refs completely.
Signed-off-by: Johan Herland <johan@herland.net>
Acked-by: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
In repos with many refs, it is unlikely that most refs will ever change.
This fact is already exploited by "git gc" by executing "git pack-refs"
to consolidate all refs into a single file.
When cloning a repo with many refs, it does not make sense to create the
loose refs in the first place, just to have the next "git gc" consolidate
them into one file. Instead, make "git clone" create the packed refs file
immediately, and forego the loose refs completely.
Signed-off-by: Johan Herland <johan@herland.net>
Acked-by: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin-clone.c | diffblobblamehistory |