ekazakov · August 29, 2015 14:09 · Nov 19, 2014 · Nov 11, 2014 · Nov 11, 2014 · Nov 11, 2014
diff --git a/gistfile1.sh b/gistfile1.sh
@@ -12,6 +12,5 @@
 # aren't errors. If it prints "OK" at the end, your repos are all valid.
 
 # Please leave a comment here saying whether the command succeeded or not (even
-# if it said "OK"!) If it failed, please paste the bottom of the error,
-# starting with the last "git fsck" command, and also indicate what OS and file
-# system you run.
+# if it said "OK"!). Also name your OS and file system. If it failed, please
+# paste the bottom of the error, starting with the last "git fsck" command.
diff --git a/gistfile1.sh b/gistfile1.sh
@@ -2,13 +2,16 @@
 
 # cd to the directory containing your project repositories and run the command
 # below. (It's long; make sure you get it all.) It finds all of your git repos
-# and runs paranoid fscks in them.
+# and runs paranoid fscks in them to check their integrity.
 
 (set -e && find . -type d -and -iname '.git' | while read p; do (cd "$(dirname "$p")" && (set -x && git fsck --full --strict)); done) && echo "OK"
 
 # I have 81 git repos in my ~/proj directory and had no errors.
 
-# Please leave a comment here saying whether errors were found (if not, it will
-# say "OK!" at the end). If it failed, please paste the bottom of the error,
+# You might get messages about dangling commits, dangling blobs, etc. Those
+# aren't errors. If it prints "OK" at the end, your repos are all valid.
+
+# Please leave a comment here saying whether the command succeeded or not (even
+# if it said "OK"!) If it failed, please paste the bottom of the error,
 # starting with the last "git fsck" command, and also indicate what OS and file
 # system you run.
diff --git a/gistfile1.sh b/gistfile1.sh
@@ -1,7 +1,8 @@
 # Has your OS/FS/disk lost your data?
 
 # cd to the directory containing your project repositories and run the command
-# below. (It's long; make sure you get it all.)
+# below. (It's long; make sure you get it all.) It finds all of your git repos
+# and runs paranoid fscks in them.
 
 (set -e && find . -type d -and -iname '.git' | while read p; do (cd "$(dirname "$p")" && (set -x && git fsck --full --strict)); done) && echo "OK"
 

diff --git a/gistfile1.sh b/gistfile1.sh
@@ -8,5 +8,6 @@
 # I have 81 git repos in my ~/proj directory and had no errors.
 
 # Please leave a comment here saying whether errors were found (if not, it will
-# say "OK!" at the end). If it failed, please paste the relevant bits of the
-# error, along with which OS and file system you run.
+# say "OK!" at the end). If it failed, please paste the bottom of the error,
+# starting with the last "git fsck" command, and also indicate what OS and file
+# system you run.
diff --git a/gistfile1.sh b/gistfile1.sh
@@ -9,4 +9,4 @@
 
 # Please leave a comment here saying whether errors were found (if not, it will
 # say "OK!" at the end). If it failed, please paste the relevant bits of the
-# error.
+# error, along with which OS and file system you run.
diff --git a/gistfile1.sh b/gistfile1.sh
@@ -0,0 +1,12 @@
+# Has your OS/FS/disk lost your data?
+
+# cd to the directory containing your project repositories and run the command
+# below. (It's long; make sure you get it all.)
+
+(set -e && find . -type d -and -iname '.git' | while read p; do (cd "$(dirname "$p")" && (set -x && git fsck --full --strict)); done) && echo "OK"
+
+# I have 81 git repos in my ~/proj directory and had no errors.
+
+# Please leave a comment here saying whether errors were found (if not, it will
+# say "OK!" at the end). If it failed, please paste the relevant bits of the
+# error.