and it can skip files that match exclude rules i suppose
+ /some/file
c /another/file
s /some/path
or maybe a for add
so add, cached and skipped
What would "cached" mean? And will there be a distinction between "added" and "updated"?
and doesn't resend that
so cached is just a file it knows it already send last time
that makes sense
put /dir/added
skip /dir/skipped
exclude /dir/excluded
maybe
do you think times are useful?
I mean, sometimes. But eeh
the file actions are not quite so straight forward, since only files are ever 'skipped', as they are the only things that have data that can be skipped
Because you always walk all directories (except when they're excluded)?
then it pushes all dirs into the work list
the current progress bar just shows when it is processing a whole directory
its definitely easy to just print the paths as we process them
just harder to exactly summarize it
i can see why exclusions are especially useful to see
d /dir
f /file
d* /dir-contributing-to-cache-hit
f* /cached-file
x /excluded-path
this way you can kind of see how effective the stat cache is being
and what is being excluded
and maybe ! or something for modification detected
thats the case where you are uploading a file
and it changes while you are uploading it
but it doesn't cache that file
if bupstash stats a file, but then you delete it
bupstash pretends that file never existed and skips it
so, it tries to carry on
originally bupstash would abort and restart your backup
but that caused a lot of other problems too
so, in practice its like tar, you shouldn't really do a backup on live data
but its gonna try it's best
perhaps a slightly smeared backup is better than nothing