aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@citi.umich.edu>2007-01-26 00:17:12 -0500
committerJ. Bruce Fields <bfields@citi.umich.edu>2007-01-26 00:17:12 -0500
commit11e016a32c1ac5535a9a248e23bc9a7e1f6c43d2 (patch)
tree6119f5b903a89fb6ceda08a3af6f40dbe6c4bdcf
parent17217090cf92e094f711359d92196e8129e3281c (diff)
downloadgit-11e016a32c1ac5535a9a248e23bc9a7e1f6c43d2.tar.gz
git-11e016a32c1ac5535a9a248e23bc9a7e1f6c43d2.tar.xz
user-manual: stub discussion of fsck and reflog
Have some sort of recovery/reliability section that deals with reflog and fsck. Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
-rw-r--r--Documentation/user-manual.txt21
1 files changed, 21 insertions, 0 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 30adc72dc..00e445d30 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -1456,6 +1456,27 @@ $ git gc
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.
+Ensuring reliability
+--------------------
+
+Checking the repository for corruption
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+TODO:
+ git-fsck
+ "dangling objects" explanation
+ Brief explanation here,
+ include forward reference to longer explanation from
+ Linus, to be added to later chapter
+
+Recovering lost changes
+~~~~~~~~~~~~~~~~~~~~~~~
+
+TODO:
+ reflog
+ git-fsck
+ low-level examination of objects
+
Sharing development with others
===============================