aboutsummaryrefslogtreecommitdiff
path: root/exec_cmd.c
diff options
context:
space:
mode:
authorBrandon Casey <casey@nrlssc.navy.mil>2009-01-09 16:14:39 -0600
committerJunio C Hamano <gitster@pobox.com>2009-01-17 23:44:33 -0800
commita83c88525ed6d8d940f8cf7f21e92b189f7844e3 (patch)
tree67c0dad263cb13553c99e137147bca2a853c3d93 /exec_cmd.c
parent7a38329130f05e00ad73c2794d94b869f16bca2f (diff)
downloadgit-a83c88525ed6d8d940f8cf7f21e92b189f7844e3.tar.gz
git-a83c88525ed6d8d940f8cf7f21e92b189f7844e3.tar.xz
t7700: demonstrate misbehavior of 'repack -a' when local packs exist
The ability to "...fatten [the] local repository by packing everything that is needed by the local ref into a single new pack, including things that are borrowed from alternates"[1] is supposed to be provided by the '-a' or '-A' options to repack when '-l' is not used, but there is a flaw. For each pack in the local repository without a .keep file, repack supplies a --unpacked=<pack> argument to pack-objects. The --unpacked option to pack-objects, with or without an argument, causes pack-objects to ignore any object which is packed in a pack not mentioned in an argument to --unpacked=. So, if there are local packs, and 'repack -a' is called, then any objects which reside in packs accessible through alternates will _not_ be packed. If there are no local packs, then no --unpacked argument will be supplied, and repack will behave as expected. [1] http://mid.gmane.org/7v8wrwidi3.fsf@gitster.siamese.dyndns.org Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'exec_cmd.c')
0 files changed, 0 insertions, 0 deletions