Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
user-manual: update git-gc discussion
author
J. Bruce Fields
<bfields@citi.umich.edu>
Mon, 22 Jan 2007 04:03:36 +0000
(23:03 -0500)
committer
J. Bruce Fields
<bfields@citi.umich.edu>
Mon, 22 Jan 2007 04:03:36 +0000
(23:03 -0500)
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>
Documentation/user-manual.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
f60b964
)
diff --git
a/Documentation/user-manual.txt
b/Documentation/user-manual.txt
index 6c858aaddc72a4ffcb23bb7e537bc2845fea8fb2..30adc72dce4f9dae7f676065be6f36644ca07974 100644
(file)
--- a/
Documentation/user-manual.txt
+++ b/
Documentation/user-manual.txt
@@
-1447,16
+1447,14
@@
On large repositories, git depends on compression to keep the history
information from taking up to much space on disk or in memory.
This compression is not performed automatically. Therefore you
information from taking up to much space on disk or in memory.
This compression is not performed automatically. Therefore you
-should occasionally run
+should occasionally run
gitlink:git-gc[1]:
-------------------------------------------------
$ git gc
-------------------------------------------------
-------------------------------------------------
$ git gc
-------------------------------------------------
-to recompress the archive and to prune any commits which are no
-longer referred to anywhere. This can be very time-consuming, and
-you should not modify the repository while it is working, so you
-should run it while you are not working.
+to recompress the archive. This can be very time-consuming, so
+you may prefer to run git-gc when you are not doing other work.
Sharing development with others
===============================
Sharing development with others
===============================