TW
No news here.
superseded by #7063, closing this.
Guess I rather won't backport that: - widespread changes - changing the option name would break scripts - master patches likely can't be cherry-picked easily due to master now being...
If somebody else wants to do a backport to 1.2-maint branch, I guess it would be acceptable if: - all the renaming i did in master branch is **not** done...
some ideas from today's perspective: - the above bug (this issue here, #6740) is still not clear - if you can reproduce it with borg 1.2.2, please post a new...
1.2.2 is available from the borgbackup ppa and also from the github releases page here.
I edited the title slightly to reflect that we currently only have evidence about this happening with borg 1.2.0 (and cifs).
The obvious place to output the quota information is `borg info` I'ld say. Not a big fan from putting more and more into borg create output.
Guess the best idea yet was: - do not put the python code into the global python `site-packages`, but have them in a private space of borg1 and borg 2....
#7037 is doing repo-wide recompression. i didn't even need the flags because the ctype/clevel is in the now separately available metadata.