Big tool rename.

[thirdparty/git.git] / Documentation / git-fsck-objects.txt

diff --git a/Documentation/git-fsck-cache.txt b/Documentation/git-fsck-objects.txt
similarity index 88%
rename from Documentation/git-fsck-cache.txt
rename to Documentation/git-fsck-objects.txt
index 13f19653febee23a673fb87e0399fd65a3b29707..2b8640439b94fe41aac561b1449dbd1c4fdaf2f0 100644 (file)
--- a/Documentation/git-fsck-cache.txt
+++ b/Documentation/git-fsck-objects.txt
@@ -1,15 +1,15 @@
-git-fsck-cache(1)
-=================
+git-fsck-objects(1)
+===================
 v0.1, May 2005
 
 NAME
 ----
-git-fsck-cache - Verifies the connectivity and validity of the objects in the database
+git-fsck-objects - Verifies the connectivity and validity of the objects in the database
 
 
 SYNOPSIS
 --------
-'git-fsck-cache' [--tags] [--root] [--unreachable] [--cache] [--standalone | --full] [--strict] [<object>*]
+'git-fsck-objects' [--tags] [--root] [--unreachable] [--cache] [--standalone | --full] [--strict] [<object>*]
 
 DESCRIPTION
 -----------
@@ -20,7 +20,7 @@ OPTIONS
 <object>::
        An object to treat as the head of an unreachability trace.
 
-       If no objects are given, git-fsck-cache defaults to using the
+       If no objects are given, git-fsck-objects defaults to using the
        index file and all SHA1 references in .git/refs/* as heads.
 
 --unreachable::
@@ -69,11 +69,11 @@ that aren't readable from any of the specified head nodes.
 
 So for example
 
-       git-fsck-cache --unreachable $(cat .git/HEAD .git/refs/heads/*)
+       git-fsck-objects --unreachable $(cat .git/HEAD .git/refs/heads/*)
 
 will do quite a _lot_ of verification on the tree. There are a few
 extra validity tests to be added (make sure that tree objects are
-sorted properly etc), but on the whole if "git-fsck-cache" is happy, you
+sorted properly etc), but on the whole if "git-fsck-objects" is happy, you
 do have a valid tree.
 
 Any corrupt objects you will have to find in backups or other archives
@@ -111,7 +111,7 @@ dangling <type> <object>::
        The <type> object <object>, is present in the database but never
        'directly' used. A dangling commit could be a root node.
 
-warning: git-fsck-cache: tree <tree> has full pathnames in it::
+warning: git-fsck-objects: tree <tree> has full pathnames in it::
        And it shouldn't...
 
 sha1 mismatch <object>::