@matheusbsbs / matheus-bagliano / commits / 04e50e9457
Fork 0

user-manual: fsck-objects -> fsck

There seems to be an agreement to rename fsck-objects to fsck. Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>

J. Bruce Fields committed Jan 28, 2007 at 23:31 UTC 04e50e94570cc2e71abe0451723fbd89e4893c5f
1 file changed +8 -8
Documentation/user-manual.txt
+8 -8
@@ -238,7 +238,7 @@ Repository maintenance
238 Check for corruption:
239
240 -----------------------------------------------
241 -$ git fsck-objects
241 +$ git fsck
242 -----------------------------------------------
243
244 Recompress, remove unused cruft:
@@ -1373,12 +1373,12 @@ Ensuring reliability
1373 Checking the repository for corruption
1374 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1375
1376 -The gitlink:git-fsck-objects[1] command runs a number of self-consistency
1376 +The gitlink:git-fsck[1] command runs a number of self-consistency
1377 checks on the repository, and reports on any problems. This may take some
1378 time. The most common warning by far is about "dangling" objects:
1379
1380 -------------------------------------------------
1381 -$ git fsck-objects
1381 +$ git fsck
1382 dangling commit 7281251ddd2a61e38657c827739c57015671a6b3
1383 dangling commit 2706a059f258c6b245f298dc4ff2ccd30ec21a63
1384 dangling commit 13472b7c4b80851a1bc551779171dcb03655e9b5
@@ -2126,7 +2126,7 @@ size> + <byte\0> + <binary object data>.
2126
2127 The structured objects can further have their structure and
2128 connectivity to other objects verified. This is generally done with
2129 -the `git-fsck-objects` program, which generates a full dependency graph
2129 +the `git-fsck` program, which generates a full dependency graph
2130 of all objects, and verifies their internal consistency (in addition
2131 to just verifying their superficial consistency through the hash).
2132
@@ -2722,7 +2722,7 @@ you, so is normally the only high-level command you need.
2722 Dangling objects
2723 ^^^^^^^^^^^^^^^^
2724
2725 -The gitlink:git-fsck-objects[1] command will sometimes complain about dangling
2725 +The gitlink:git-fsck[1] command will sometimes complain about dangling
2726 objects. They are not a problem.
2727
2728 The most common cause of dangling objects is that you've rebased a branch, or
@@ -2797,9 +2797,9 @@ and they'll be gone. But you should only run "git prune" on a quiescent
2797 repository - it's kind of like doing a filesystem fsck recovery: you don't
2798 want to do that while the filesystem is mounted.
2799
2800 -(The same is true of "git-fsck-objects" itself, btw - but since
2801 -git-fsck-objects never actually *changes* the repository, it just reports
2802 -on what it found, git-fsck-objects itself is never "dangerous" to run.
2800 +(The same is true of "git-fsck" itself, btw - but since
2801 +git-fsck never actually *changes* the repository, it just reports
2802 +on what it found, git-fsck itself is never "dangerous" to run.
2803 Running it while somebody is actually changing the repository can cause
2804 confusing and scary messages, but it won't actually do anything bad. In
2805 contrast, running "git prune" while somebody is actively changing the