summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web>2011-06-13 18:09:58 +0000
committerGravatar admin <admin@branchable.com>2011-06-13 18:09:58 +0000
commit056a784f3d747809c6f256603ff0f8cfb9f6c042 (patch)
treee267d5fb24aee4be055f275e90a350efacedb815
parenteb5fbc4cb97b73ad5d5d194600cc52c99edc89a0 (diff)
-rw-r--r--doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn b/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn
index b6ff6bba1..249a17505 100644
--- a/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn
+++ b/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn
@@ -10,3 +10,6 @@ See http://lists.madduck.net/pipermail/vcs-home/2011-June/000433.html
> So this may be another thing blocked by [[todo/branching]], assuming
> that is fixed in a way that makes `.git-annex` available to bare repos.
> --[[Joey]]
+
+>> Even if there is nothing it can _do_, knowing that the data is intact,
+>> or not, is valuable in and as of itself. -- RichiH