git-repack.txt: Clarify implications of -a for dumb protocols
The current text makes some users feel uneasy, worrying whether '-a' could lead to corrupt repositories. Clarify that '-a' may lead to performance issues only for dumb protocols. Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> Helped-by: Stephen Boyd <bebarino@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Michael J Gruber committed
Jun 9, 2009 at 18:15 UTC
9a8531eeba5053281e14ef14e6beb019ce17f07e
1 file changed
+5
-2
Documentation/git-repack.txt
+5
-2
@@ -31,11 +31,14 @@ OPTIONS
31
Instead of incrementally packing the unpacked objects,
32
pack everything referenced into a single pack.
33
Especially useful when packing a repository that is used
34
- for private development and there is no need to worry
35
- about people fetching via dumb protocols from it. Use
34
+ for private development. Use
35
with '-d'. This will clean up the objects that `git prune`
36
leaves behind, but `git fsck --full` shows as
37
dangling.
38
++
39
+Note that users fetching over dumb protocols will have to fetch the
40
+whole new pack in order to get any contained object, no matter how many
41
+other objects in that pack they already have locally.
42
43
-A::
44
Same as `-a`, unless '-d' is used. Then any unreachable