author | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 8 Nov 2006 01:40:35 +0000 (20:40 -0500) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 8 Nov 2006 04:48:21 +0000 (23:48 -0500) | ||
commit | d1536c488e2f410c9f622356e29d9a5870d2403f | |
tree | 2b0dafb4f9f4e4605aa0f45ca3baef65c1b2fb8f | tree | snapshot |
parent | 0fb8f9ce05bf65cc9c22f078c4a6dc7dec3ec27a | commit | diff |
git-gui: Added repack database menu option, to invoke git repack.
Most users of git-gui probably shouldn't be invoking git repack directly;
instead we should be looking at how many loose objects they have and
how many active packs they have and making the decision for them. But
that's more work to code, and there's always going to be discussion about
what is the right default threshold and how do we know that the user is
willing to do the repack when we decide its time, etc.
So instead we'll just keep it simple and offer up the menu option.
Unfortunately right now we get now progress indication back from
git-pack-objects as its being invoked not through a tty, which makes
it disable progress output and the git-repack.sh wrapper won't let us
pass through --progress.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Most users of git-gui probably shouldn't be invoking git repack directly;
instead we should be looking at how many loose objects they have and
how many active packs they have and making the decision for them. But
that's more work to code, and there's always going to be discussion about
what is the right default threshold and how do we know that the user is
willing to do the repack when we decide its time, etc.
So instead we'll just keep it simple and offer up the menu option.
Unfortunately right now we get now progress indication back from
git-pack-objects as its being invoked not through a tty, which makes
it disable progress output and the git-repack.sh wrapper won't let us
pass through --progress.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
git-gui | diff | blob | history |