From 81de608447b0334ef84ebd74c380e4d0b3f6481b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 22 Oct 2013 16:30:39 -0400 Subject: devblog --- doc/devblog/day_41__onward.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/devblog/day_41__onward.mdwn (limited to 'doc') diff --git a/doc/devblog/day_41__onward.mdwn b/doc/devblog/day_41__onward.mdwn new file mode 100644 index 000000000..4ee27c92c --- /dev/null +++ b/doc/devblog/day_41__onward.mdwn @@ -0,0 +1,15 @@ +I think that git-recover-repository is ready now. Made it deal with the +index file referencing corrupt objects. The best approach I could think of +for that is to just remove those objects from the index, so the user can +re-add files from their work tree after recovery. + +Now to integrate this git repository repair capability into the git-annex +assistant. I decided to run `git fsck` as part of a scheduled +repository consistency check. It may also make sense for the assistant to +notice when things are going wrong, and suggest an immediate check. I've +started on the webapp UI to run a repository repair when fsck detects +problems. + +[[!img /assistant/brokenrepositoryalert.png]] + +[[!img /assistant/repairrepository.png]] -- cgit v1.2.3