Linus Torvalds <torvalds@xxxxxxxx> writes: > However, now that rebasing ends up being visible in the branch reflog, > we're back to the "normally nothing to ever prune" situation, and as such, > the only object pruning that _should_ take place is basically as part of > "git repack -a -d" (which unlike a prune is actually safe, since it only > prunes objects that are reachable from a pack). > > So to recap: "git prune" simply isn't a safe thing to do. Don't do it > without thinking. I'm not at all sure it's a good idea that "git gc" does > it for you, since it just encourages mindless pruning that probably > shouldn't happen in the first place. I guess we are in agreement on this. -- >8 -- [PATCH] git-gc: do not run prune mindlessly. Signed-off-by: Junio C Hamano <junkio@xxxxxxx> --- Documentation/git-gc.txt | 1 - git-gc.sh | 1 - 2 files changed, 0 insertions(+), 2 deletions(-) diff --git a/Documentation/git-gc.txt b/Documentation/git-gc.txt index 2bcc949..f53ca97 100644 --- a/Documentation/git-gc.txt +++ b/Documentation/git-gc.txt @@ -50,7 +50,6 @@ kept. This defaults to 15 days. See Also -------- -gitlink:git-prune[1] gitlink:git-reflog[1] gitlink:git-repack[1] gitlink:git-rerere[1] diff --git a/git-gc.sh b/git-gc.sh index 6de55f7..7716f62 100755 --- a/git-gc.sh +++ b/git-gc.sh @@ -11,5 +11,4 @@ SUBDIRECTORY_OK=Yes git-pack-refs --prune && git-reflog expire --all && git-repack -a -d -l && -git-prune && git-rerere gc || exit -- 1.5.0.rc2 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html