summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-08-01 23:51:48 +0000
committerGravatar admin <admin@branchable.com>2013-08-01 23:51:48 +0000
commit8210a152ff57a2738f2c914734f5380458c9d7c4 (patch)
tree74f06b65c80f5b791043c8e0b0da9f4da1bbe4fb /doc
parentcb19cf77b8c811cf9ea22839d2a1070b52ec6c7c (diff)
Added a comment
Diffstat (limited to 'doc')
-rw-r--r--doc/special_remotes/hook/comment_9_037523d1994c702239ca96791156fe65._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/special_remotes/hook/comment_9_037523d1994c702239ca96791156fe65._comment b/doc/special_remotes/hook/comment_9_037523d1994c702239ca96791156fe65._comment
new file mode 100644
index 000000000..89719adfb
--- /dev/null
+++ b/doc/special_remotes/hook/comment_9_037523d1994c702239ca96791156fe65._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="4.152.108.145"
+ subject="comment 9"
+ date="2013-08-01T23:51:48Z"
+ content="""
+The behavior you show with `fsck --from` is that the first time it's run against the damaged remote it notices the file is not present using the checkpresent hook. It then updates the location log. The subsequent times it's run, it sees that the location log says the file is not present in the remote. It verifies this is the case by calling the checkpresent hook. Since the two data sources agree, and numcopies is still satisfied, it prints \"ok\". There does not seem to be a bug here.
+
+(`return` in Haskell does not do what you would expect to happen in a traditional imperative language. It does not alter control flow, and any function using `return` can be mechanically converted to one that does not use `return`.)
+"""]]