summaryrefslogtreecommitdiff
path: root/doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn')
-rw-r--r--doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn22
1 files changed, 0 insertions, 22 deletions
diff --git a/doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn b/doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn
deleted file mode 100644
index a3beaadae..000000000
--- a/doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-I would like to be able to name a few remotes that must retain *all* annexed
-files. `git-annex fsck` should warn me if any files are missing from those
-remotes, even if `annex.numcopies` has been satisfied by other remotes.
-
-I imagine this could also be useful for bup remotes, but I haven't actually
-looked at those yet.
-
-Based on existing output, this is what a warning message could look like:
-
- fsck FILE
- 3 of 3 trustworthy copies of FILE exist.
- FILE is, however, still missing from these required remotes:
- UUID -- Backup Drive 1
- UUID -- Backup Drive 2
- Back it up with git-annex copy.
- Warning
-
-What do you think?
-
-> I think that [[required_content]] will make it easy to configure
-> such remotes, so this is another reason to build that. Closing
-> this bug as a dup of that one; [[done]] --[[Joey]]