author | Jeff King <peff@peff.net> | |
Tue, 29 Apr 2008 20:45:14 +0000 (16:45 -0400) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 30 Apr 2008 06:11:57 +0000 (23:11 -0700) | ||
commit | 8d308b35401b6abebb65aa97a322526ae11d7220 | |
tree | 0ac12a1d8ac7b0847fffeb6c0d9f2e7a377e3cff | tree | snapshot |
parent | 302cc11a32732a0a3f0a7875b1857098e1964929 | commit | diff |
Documentation: point git-prune users to git-gc
Most users should be using git-gc instead of directly
calling prune. For those who really do want more information
on pruning, let's point them at git-fsck, which goes into
slightly more detail on reachability.
And since we're pointing users there, let's make sure
reflogs are mentioned in git-fsck(1).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Most users should be using git-gc instead of directly
calling prune. For those who really do want more information
on pruning, let's point them at git-fsck, which goes into
slightly more detail on reachability.
And since we're pointing users there, let's make sure
reflogs are mentioned in git-fsck(1).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-fsck.txt | diff | blob | history | |
Documentation/git-prune.txt | diff | blob | history |