diff options
author | J. Bruce Fields <bfields@citi.umich.edu> | 2007-01-21 23:03:36 -0500 |
---|---|---|
committer | J. Bruce Fields <bfields@citi.umich.edu> | 2007-01-21 23:03:36 -0500 |
commit | 17217090cf92e094f711359d92196e8129e3281c (patch) | |
tree | c00d8e62f0ab4ffd79c4ac49e8c8fbab1b684a3c | |
parent | f60b964249fb38fea7906559875c600665a2d991 (diff) | |
download | git-17217090cf92e094f711359d92196e8129e3281c.tar.gz |
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>
-rw-r--r-- | Documentation/user-manual.txt | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 6c858aaddc..30adc72dce 100644 --- 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 -should occasionally run +should occasionally run gitlink:git-gc[1]: ------------------------------------------------- $ 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 =============================== |