summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar andy <andy@web>2013-02-08 06:27:59 +0000
committerGravatar admin <admin@branchable.com>2013-02-08 06:27:59 +0000
commite0eb486a63ecaec74f36f056e3ccf2ef0a544520 (patch)
tree23531db39bedafe6601c88419e9601298c829e68
parent38dbc9667f80b3566eef5138e436d30cb5ad409c (diff)
-rw-r--r--doc/forum/Feature_request:_git_annex_copy_--auto_does_the_right_thing.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/Feature_request:_git_annex_copy_--auto_does_the_right_thing.mdwn b/doc/forum/Feature_request:_git_annex_copy_--auto_does_the_right_thing.mdwn
new file mode 100644
index 000000000..0a069340c
--- /dev/null
+++ b/doc/forum/Feature_request:_git_annex_copy_--auto_does_the_right_thing.mdwn
@@ -0,0 +1,5 @@
+I'm not sure of the right place for feature requests; sorry if this is incorrect.
+
+It occurred to me that it would be neat if running git annex copy --auto copied enough copies of the file to connected remotes that don't have it to fulfil numcopies (if possible). Further coolness could come from choosing the remotes smartly (based, for example, on availability, access cost, remote disk space, trust level... you get the idea)
+
+Having an option like this would allow the user to use numcopies to backup files to wherever possible, if they don't really care about where those copies go.