git-commit-vandalism/contrib/examples/git-gc.sh

#!/bin/sh
#
# Copyright (c) 2006, Shawn O. Pearce
#
# Cleanup unreachable files and optimize the repository.

USAGE='[--prune]'
SUBDIRECTORY_OK=Yes
. git-sh-setup

no_prune=:
while test $# != 0
do
	case "$1" in
	--prune)
		no_prune=
		;;
	--)
		usage
		;;
	esac
	shift
done

case "$(git config --get gc.packrefs)" in
notbare|"")
	test $(is_bare_repository) = true || pack_refs=true;;
*)
	pack_refs=$(git config --bool --get gc.packrefs)
esac

test "true" != "$pack_refs" ||
git pack-refs --prune &&
git reflog expire --all &&
git-repack -a -d -l &&
$no_prune git prune &&
git rerere gc || exit
Create 'git gc' to perform common maintenance operations. Junio asked for a 'git gc' utility which users can execute on a regular basis to perform basic repository actions such as: * pack-refs --prune * reflog expire * repack -a -d * prune * rerere gc So here is a command which does exactly that. The parameters fed to reflog's expire subcommand can be chosen by the user by setting configuration options in .git/config (or ~/.gitconfig), as users may want different expiration windows for each repository but shouldn't be bothered to remember what they are all of the time. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <junkio@cox.net> 2006-12-27 08:17:59 +01:00			`#!/bin/sh`
			`#`
			`# Copyright (c) 2006, Shawn O. Pearce`
			`#`
			`# Cleanup unreachable files and optimize the repository.`

Fix git-gc usage note Signed-off-by: Matthias Kestenholz <matthias@spinlock.ch> Signed-off-by: Junio C Hamano <junkio@cox.net> 2007-03-03 18:28:14 +01:00			`USAGE='[--prune]'`
Create 'git gc' to perform common maintenance operations. Junio asked for a 'git gc' utility which users can execute on a regular basis to perform basic repository actions such as: * pack-refs --prune * reflog expire * repack -a -d * prune * rerere gc So here is a command which does exactly that. The parameters fed to reflog's expire subcommand can be chosen by the user by setting configuration options in .git/config (or ~/.gitconfig), as users may want different expiration windows for each repository but shouldn't be bothered to remember what they are all of the time. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <junkio@cox.net> 2006-12-27 08:17:59 +01:00			`SUBDIRECTORY_OK=Yes`
			`. git-sh-setup`

git-gc: do not run git-prune by default. 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> 2007-01-22 08:28:28 +01:00			`no_prune=:`
Supplant the "while case ... break ;; esac" idiom A lot of shell scripts contained stuff starting with while case "$#" in 0) break ;; esac and similar. I consider breaking out of the condition instead of the body od the loop ugly, and the implied "true" value of the non-matching case is not really obvious to humans at first glance. It happens not to be obvious to some BSD shells, either, but that's because they are not POSIX-compliant. In most cases, this has been replaced by a straight condition using "test". "case" has the advantage of being faster than "test" on vintage shells where "test" is not a builtin. Since none of them is likely to run the git scripts, anyway, the added readability should be worth the change. A few loops have had their termination condition expressed differently. Signed-off-by: David Kastrup <dak@gnu.org> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2007-09-23 22:42:08 +02:00			`while test $# != 0`
git-gc: do not run git-prune by default. 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> 2007-01-22 08:28:28 +01:00			`do`
			`case "$1" in`
			`--prune)`
			`no_prune=`
			`;;`
			`--)`
			`usage`
			`;;`
			`esac`
			`shift`
			`done`

git-gc: run pack-refs by default unless the repo is bare The config variable gc.packrefs is tristate now: "true", "false" and "notbare", where "notbare" is the default. Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de> Signed-off-by: Junio C Hamano <junkio@cox.net> 2007-02-13 14:01:42 +01:00			`case "$(git config --get gc.packrefs)" in`
			`notbare\|"")`
			`test $(is_bare_repository) = true \|\| pack_refs=true;;`
			`*)`
			`pack_refs=$(git config --bool --get gc.packrefs)`
			`esac`

			`test "true" != "$pack_refs" \|\|`
Rewrite "git-frotz" to "git frotz" This uses the remove-dashes target to replace "git-frotz" to "git frotz". Signed-off-by: Junio C Hamano <gitster@pobox.com> 2007-07-03 07:52:14 +02:00			`git pack-refs --prune &&`
			`git reflog expire --all &&`
Use 'repack -a -d -l' instead of 'repack -a -d' in git-gc Otherwise we would end up slurping objects we borrow from alternates. Signed-off-by: Junio C Hamano <junkio@cox.net> 2006-12-27 23:23:21 +01:00			`git-repack -a -d -l &&`
Rewrite "git-frotz" to "git frotz" This uses the remove-dashes target to replace "git-frotz" to "git frotz". Signed-off-by: Junio C Hamano <gitster@pobox.com> 2007-07-03 07:52:14 +02:00			`$no_prune git prune &&`
			`git rerere gc \|\| exit`