From 4517e9e41ca75cfa9d51f5464f85e12f35de859e Mon Sep 17 00:00:00 2001 From: Atemu Date: Sat, 25 Jun 2022 16:36:38 +0000 Subject: [PATCH] Added a comment: Still useful --- ...ment_6_bef44c8f571f2be177d6ee949c721a6a._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/todo/Specify_maximum_usable_space_per_remote/comment_6_bef44c8f571f2be177d6ee949c721a6a._comment diff --git a/doc/todo/Specify_maximum_usable_space_per_remote/comment_6_bef44c8f571f2be177d6ee949c721a6a._comment b/doc/todo/Specify_maximum_usable_space_per_remote/comment_6_bef44c8f571f2be177d6ee949c721a6a._comment new file mode 100644 index 0000000000..dc3faefeb5 --- /dev/null +++ b/doc/todo/Specify_maximum_usable_space_per_remote/comment_6_bef44c8f571f2be177d6ee949c721a6a._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="Atemu" + avatar="http://cdn.libravatar.org/avatar/d1f0f4275931c552403f4c6707bead7a" + subject="Still useful" + date="2022-06-25T16:36:38Z" + content=""" +Implementing a hard limit concurrently isn't feasible but only providing a best-effort target size would still be useful. + +It should fully work in all non-concurrent use-cases which are the majority in my case. + +This would also open up the possibility of allowing me to know which drive I need to plug in when there is new data to be backed up because git-annex would know how much a repo is able to store and how much it currently holds. +This obviously isn't perfect either (there might be other data on that drive; other annex repos or entirely untracked data for example) but it'd still be good enough to make a manual decision on for me. +"""]]