user-manual: update git-gc discussion
It appears git-gc will no longer prune automatically, so we don't need to tell people not to do other stuff while running it. Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
J. Bruce Fields committed
Jan 21, 2007 at 23:03 UTC
17217090cf92e094f711359d92196e8129e3281c
1 file changed
+3
-5
Documentation/user-manual.txt
+3
-5
@@ -1447,16 +1447,14 @@ On large repositories, git depends on compression to keep the history
1447
information from taking up to much space on disk or in memory.
1448
1449
This compression is not performed automatically. Therefore you
1450
-should occasionally run
1450
+should occasionally run gitlink:git-gc[1]:
1451
1452
-------------------------------------------------
1453
$ git gc
1454
-------------------------------------------------
1455
1456
-to recompress the archive and to prune any commits which are no
1457
-longer referred to anywhere. This can be very time-consuming, and
1458
-you should not modify the repository while it is working, so you
1459
-should run it while you are not working.
1456
+to recompress the archive. This can be very time-consuming, so
1457
+you may prefer to run git-gc when you are not doing other work.
1458
1459
Sharing development with others
1460
===============================