Hi,
On 14/05/2021 09:29, griffin tucker wrote:
i can try drafting some pseudo-code, but by the looks of things, it'd
take some major restructuring - not impossible, though!
I never said that it's impossible, but "major restructuring" is indeed
in progress, and "not very difficult" is
i can try drafting some pseudo-code, but by the looks of things, it'd
take some major restructuring - not impossible, though!
i'll have a better look through the source to see if it's feasible -
another option i'd want is to compress the last backup, not just the
diffs, as well as choice of
Hi,
On 14/05/2021 08:42, griffin tucker wrote:
> i don't think it's very difficult to implement this, just a matter of doing
> an initial list of all files, tallying their file sizes, then comparing
> this list to what's already in the backup (for missing/changed files, etc.)
It's open source so
that's a good idea to use -v5, however in my use case i have lots of small
files and a few very large files.
google search suggestions seems to indicate that it's a feature that many
people are looking for.
i don't think it's very difficult to implement this, just a matter of doing
an initial
I doubt it, it wouldn't be very helpful and very synthetic if at all possible.
I personally use rdiff-backup with -v5 and the alphabetic order of the files
tells me where the backup has (roughly) arrived.
KR, Eric
On April 26, 2021 8:10:13 AM UTC, griffin tucker
wrote:
>would a progress bar
