e3ff4b2447
git-prune is not safe when run uncontrolled in parallel while other git operations are creating new objects. To avoid mistakes, do not run git-prune by default from git-gc. Signed-off-by: Junio C Hamano <junkio@cox.net>
30 lines
417 B
Bash
Executable File
30 lines
417 B
Bash
Executable File
#!/bin/sh
|
|
#
|
|
# Copyright (c) 2006, Shawn O. Pearce
|
|
#
|
|
# Cleanup unreachable files and optimize the repository.
|
|
|
|
USAGE='git-gc [--prune]'
|
|
SUBDIRECTORY_OK=Yes
|
|
. git-sh-setup
|
|
|
|
no_prune=:
|
|
while case $# in 0) break ;; esac
|
|
do
|
|
case "$1" in
|
|
--prune)
|
|
no_prune=
|
|
;;
|
|
--)
|
|
usage
|
|
;;
|
|
esac
|
|
shift
|
|
done
|
|
|
|
git-pack-refs --prune &&
|
|
git-reflog expire --all &&
|
|
git-repack -a -d -l &&
|
|
$no_prune git-prune &&
|
|
git-rerere gc || exit
|