mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Added a comment: Still useful

Browse source
This commit is contained in:
Atemu 2022-06-25 16:36:38 +00:00 committed by admin
parent 5df133c457
commit 4517e9e41c
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/todo/Specify_maximum_usable_space_per_remote/comment_6_bef44c8f571f2be177d6ee949c721a6a._comment Normal file
View file

@ -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.
"""]]