diff options
author | Joey Hess <joey@kitenet.net> | 2013-10-22 16:30:39 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2013-10-22 16:30:39 -0400 |
commit | 81de608447b0334ef84ebd74c380e4d0b3f6481b (patch) | |
tree | f944dbc892361029393b0b3813d7cb94a8cb4159 /doc/devblog/day_41__onward.mdwn | |
parent | ab8e457f99ebe309d6155607026051e52f59216d (diff) |
devblog
Diffstat (limited to 'doc/devblog/day_41__onward.mdwn')
-rw-r--r-- | doc/devblog/day_41__onward.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
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]] |