From 39ae33386d0b2b3f55a766839e1eabfded3a28e9 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 15 Jul 2011 12:53:58 -0400 Subject: update --- doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn') 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 249a17505..3fd1a8082 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 @@ -13,3 +13,7 @@ See http://lists.madduck.net/pipermail/vcs-home/2011-June/000433.html >> Even if there is nothing it can _do_, knowing that the data is intact, >> or not, is valuable in and as of itself. -- RichiH + +>>> While storing the data is no longer an issue in bare repos, fsck would +>>> need a special mode that examines all the location logs, since it +>>> cannot run thru the checked out files. --[[Joey]] -- cgit v1.2.3