diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-01-31 13:01:55 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-01-31 13:01:55 -0400 |
| commit | 34c1c035354ad7101d50f5854b20f6091b1945f2 (patch) | |
| tree | 5e6c6fc8e363bcc3f4a7f3b316ea9710ffb1f9f1 | |
| parent | c045f6e0914aa3ef373de0c4d3d7c2e99c721477 (diff) | |
comment
This commit was sponsored by Ole-Morten on Patreon.
| -rw-r--r-- | doc/todo/Wishlist__58___Parity_files_on_all_files/comment_1_3900fa7c3ed1455fe07d097c3dc0c9f2._comment | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/todo/Wishlist__58___Parity_files_on_all_files/comment_1_3900fa7c3ed1455fe07d097c3dc0c9f2._comment b/doc/todo/Wishlist__58___Parity_files_on_all_files/comment_1_3900fa7c3ed1455fe07d097c3dc0c9f2._comment new file mode 100644 index 000000000..86b1111d9 --- /dev/null +++ b/doc/todo/Wishlist__58___Parity_files_on_all_files/comment_1_3900fa7c3ed1455fe07d097c3dc0c9f2._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-01-31T16:55:27Z" + content=""" +git repositories don't contain parity files for their data. Instead, git +relies on multiple copies of the repository to keep things safe. Not as +efficient as parity files, but a lot easier, and protects against many more +disasters than do parity files. git-annex takes the same approach. +Lots Of Copies Keeps Stuff Safe. + +Even if git-annex started generating parity files for its objects, +the git repository would still not have them, so bit flips could still +corrupt your git-annex repository. + +Nothing stops you from writing git hooks that maintain parity files +alongside all the files in a git repository. If you do that, you'll get +parity files for the git-annex files too. But I don't see this being needed +in git-annex itself and AFAICS there are plenty of hooks in git and +git-annex to allow doing that. +"""]] |