diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2008-04-23 16:09:20 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2008-04-23 16:09:20 +0000 |
| commit | a9aee78a156ad6299451294a61aebe2a73945d3c (patch) | |
| tree | 67691d6e64c1ddd0806872a934a327873e57f53f /user-manual.txt | |
| parent | 6a45be9321b1ee81baf74de51671f224407e5ad1 (diff) | |
| download | git-htmldocs-a9aee78a156ad6299451294a61aebe2a73945d3c.tar.gz | |
Autogenerated HTML docs for v1.5.5.1-79-g57cf
Diffstat (limited to 'user-manual.txt')
| -rw-r--r-- | user-manual.txt | 17 |
1 files changed, 1 insertions, 16 deletions
diff --git a/user-manual.txt b/user-manual.txt index 565aeb980..86b91a53e 100644 --- a/user-manual.txt +++ b/user-manual.txt @@ -1548,22 +1548,7 @@ dangling tree b24c2473f1fd3d91352a624795be026d64c8841f Dangling objects are not a problem. At worst they may take up a little extra disk space. They can sometimes provide a last-resort method for -recovering lost work--see <<dangling-objects>> for details. However, if -you wish, you can remove them with linkgit:git-prune[1] or the `--prune` -option to linkgit:git-gc[1]: - -------------------------------------------------- -$ git gc --prune -------------------------------------------------- - -This may be time-consuming. Unlike most other git operations (including -git-gc when run without any options), it is not safe to prune while -other git operations are in progress in the same repository. - -If linkgit:git-fsck[1] complains about sha1 mismatches or missing -objects, you may have a much more serious problem; your best option is -probably restoring from backups. See -<<recovering-from-repository-corruption>> for a detailed discussion. +recovering lost work--see <<dangling-objects>> for details. [[recovering-lost-changes]] Recovering lost changes |