| commit | c30f9936b0e5cdced3d9cb859ce0d325ebe9c91d | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Thu, 22 May 2008 12:47:19 +0000 (22 08:47 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 23 May 2008 06:21:29 +0000 (22 23:21 -0700) | ||
| tree | a000b4e18d185cc3a9adee3373e4f999b10a319e | treesnapshot (tar.gz zip) |
| parent | 008442f5e798e511cc0cd5d9443552b0d107d558 | commitdiff |
Clarify repack -n documentation
While repacking a local repository a coworker thought the -n option
was necessary to git-repack to keep it from updating some unknown
file on the central server we all share. Explaining further what
the option is (not) doing helps to make it clear the option does
not impact any remote repositories the user may have configured.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
While repacking a local repository a coworker thought the -n option
was necessary to git-repack to keep it from updating some unknown
file on the central server we all share. Explaining further what
the option is (not) doing helps to make it clear the option does
not impact any remote repositories the user may have configured.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-repack.txt | diffblobblamehistory |