diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-10-18 15:59:58 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-10-18 15:59:58 -0400 |
| commit | 2849d9a895269d15eccbf9e93df33dca8373d1eb (patch) | |
| tree | bc15abcf6174278036041c44aed95221f52fe51f /doc/devblog | |
| parent | 4ca49833db99df1abf04c9835031925dd8ca2429 (diff) | |
devblog
Diffstat (limited to 'doc/devblog')
| -rw-r--r-- | doc/devblog/day_38__starting_git_repo_repair.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/devblog/day_38__starting_git_repo_repair.mdwn b/doc/devblog/day_38__starting_git_repo_repair.mdwn new file mode 100644 index 000000000..3808abe38 --- /dev/null +++ b/doc/devblog/day_38__starting_git_repo_repair.mdwn @@ -0,0 +1,11 @@ +Goal for the rest of the month is to build automatic recovery git +repository corruption. Spent today investigating how to do it and came up +with a fairly [[detailed_design|design/assistant/disaster_recovery]]. It +will have two parts, first to handle repository problems that can be fixed +by fetching objects from remotes, and secondly to recover from problems +where data never got sent to a remote, and has been lost. + +In either case, the assistant should be able to detect the problem and +automatically recover well enough to keep running. Since this also affects +non-git-annex repositories, it will also be available in a standalone +`git-recover-repository` command. |