author | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 27 Dec 2006 07:17:59 +0000 (02:17 -0500) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 27 Dec 2006 09:53:03 +0000 (01:53 -0800) | ||
commit | 30f610b7b09a579aeba343317114bf18b4fd92bf | |
tree | 010e90ddf832d8d51567fffc6a00aa6038d57303 | tree | snapshot |
parent | 4aec56d12ba66a321ce8a6db2ab60f81be5ccfc5 | commit | diff |
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>
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>
.gitignore | diff | blob | history | |
Documentation/git-gc.txt | [new file with mode: 0644] | blob |
Documentation/git.txt | diff | blob | history | |
Makefile | diff | blob | history | |
git-gc.sh | [new file with mode: 0755] | blob |