path: root/
AgeCommit message (Collapse)Author
2006-04-03fix repacking with lots of tagsJim Radford
Use git-rev-list's --all instead of git-rev-parse's to keep from hitting the shell's argument list length limits when repacking with lots of tags. Signed-off-by: Junio C Hamano <>
2006-03-11repack: prune loose objects when -d is givenJunio C Hamano
[jc: the request originally came from Martin Atukunda, which was improved further by Alex Riesen] Signed-off-by: Junio C Hamano <>
2006-02-17git-repack: allow passing a couple of flags to pack-objects.Junio C Hamano
A new flag -q makes underlying pack-objects less chatty. A new flag -f forces delta to be recomputed from scratch. Signed-off-by: Junio C Hamano <>
2005-12-14git-repack: Usage string clean-up, emit usage at incorrect
Signed-off-by: Fredrik Kuivinen <> Signed-off-by: Junio C Hamano <>
2005-11-25git-sh-setup: die if outside git repository.Junio C Hamano
Now all the users of this script detect its exit status and die, complaining that it is outside git repository. So move the code that dies from all callers to git-sh-setup script. Signed-off-by: Junio C Hamano <>
2005-11-21git-repack: Properly abort in corrupt repositoryLinus Torvalds
In a corrupt repository, git-repack produces a pack that does not contain needed objects without complaining, and the result of this combined with -d flag can be very painful -- e.g. a lossage of one tree object can lead to lossage of blobs reachable only through that tree. Signed-off-by: Linus Torvalds <> Signed-off-by: Junio C Hamano <>
2005-11-19git-repack: do not do complex redundancy check.Junio C Hamano
With "-a", redundant pack removal is trivial, and otherwise redundant pack removal is pointless; do not call git-redundant-pack from this script. Signed-off-by: Junio C Hamano <>
2005-11-18Remove all old packfiles when doing "git repack -a -d"Lukas Sandström
No point in running git-pack-redundant if we already know which packs are redundant. Signed-off-by: Lukas Sandström <> Signed-off-by: Junio C Hamano <>
2005-11-18git-repack: Fix variable nameRalf Baechle
Three times remove_redandant -> remove_redundant. Signed-off-by: Ralf Baechle <> Signed-off-by: Junio C Hamano <>
2005-11-12Make git-pack-redundant consider alt-odbsLukas_Sandström
This patch changes git-pack-redundant so that packfiles in alternate object directories also are considered when deciding which objects are redundant. This functionality is controlled by the flag '--alt-odb'. Also convert the other flags to the long form, and update docs and git-repack accordingly. Signed-off-by: Lukas Sandström <> Signed-off-by: Junio C Hamano <>
2005-11-12Rename git-pack-intersect to git-pack-redundantLukas_Sandström
This patch renames git-pack-intersect to git-pack-redundant as suggested by Petr Baudis. The new name reflects what the program does, rather than how it does it. Also fix a small argument parsing bug. Signed-off-by: Lukas Sandström <> Signed-off-by: Junio C Hamano <>
2005-11-12Make git-repack use git-pack-intersect.Lukas_Sandström
Signed-off-by: Lukas Sandström <> Signed-off-by: Junio C Hamano <>
2005-10-28Be marginally more careful about removing objectsLinus Torvalds
The git philosophy when it comes to disk accesses is "Laugh in the face of danger". Notably, since we never modify an existing object, we don't really care that deeply about flushing things to disk, since even if the machine crashes in the middle of a git operation, you can never really have lost any old work. At most, you'd need to figure out the proper heads (which git-fsck-objects can do for you) and re-do the operation. However, there's two exceptions to this: pruning and repacking. Those operations will actually _delete_ old objects that they know about in other ways (ie that they just repacked, or that they have found in other places). However, since they actually modify old state, we should thus be a bit more careful about them. If the machine crashes and the duplicate new objects haven't been flushed to disk, you can actually be in trouble. This is trivially stupid about it by calling "sync" before removing the objects. Not very smart, but we're talking about special operations than are usually done once a week if that. Signed-off-by: Linus Torvalds <> Signed-off-by: Junio C Hamano <>
2005-10-13Add "-l" flag for repacking only local packsLinus Torvalds
This uses the new "--local" flag to git-pack-objects. It currently only makes a difference together with "-a", since a normal incremental repack won't pack any packed objects at all (whether local or remote). Eventually, it might end up skipping any objects that aren't local to the current object directory, but for now it only knows to skip packed objects. Signed-off-by: Linus Torvalds <> Signed-off-by: Junio C Hamano <>
2005-09-18Archive-destroying "git repack -a -d" bug.Junio C Hamano
Using "git repack -a -d" can destroy your git archive if you use it twice in succession, because the new pack can be called the same as the old pack. Found by Linus. Signed-off-by: Junio C Hamano <>
2005-09-08Big tool rename.Junio C Hamano
As promised, this is the "big tool rename" patch. The primary differences since 0.99.6 are: (1) git-*-script are no more. The commands installed do not have any such suffix so users do not have to remember if something is implemented as a shell script or not. (2) Many command names with 'cache' in them are renamed with 'index' if that is what they mean. There are backward compatibility symblic links so that you and Porcelains can keep using the old names, but the backward compatibility support is expected to be removed in the near future. Signed-off-by: Junio C Hamano <>