summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-08-21 11:59:45 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-08-21 11:59:45 -0400
commitb8765b30f72401b3caaa494a9b0a4b1b8a4eab8d (patch)
tree96efd634a4dfcd3bb854fc6f27ccac36dac29dd4
parent171302db09fec70b3eb41c85e0b472787263b80e (diff)
response
-rw-r--r--doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn b/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn
index a4a802769..e15529c64 100644
--- a/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn
+++ b/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn
@@ -18,3 +18,7 @@ failed
> git-annex: reinject: 1 failed
The original file also has sha512 ead9db1f34739014a216239d9624bce74d92fe723de06505f9b94cb4c063142ba42b04546f11d3d33869b736e40ded2ff779cb32b26aa10482f09407df0f3c8d
+
+>> And what sha512 does the file in .git/annex/bad have **now**? (fsck
+>> preserves the original filename; this says nothing about what the
+>> current checksum is, if the file has been corrupted). --[[Joey]]