Closed elboulangero closed 5 years ago
How "-v" and the log levels interact is a good question. The "-v" option was supposed to be something like tar's "v" switch, i.e. just show some most high-level progress info about what we are processing (i.e. which path we are looking at). I think it would make sense to stick to that, and probably not overload it with anything else.
Right now arg_verbose is also used to show the stats at the end and a couple of other things, which I either should be removed, or also be individually selectable (since I figure running casync without path progress info but with stats should be very useful, the opposite probably not so much...)
So here's my proposal:
-s
) that only shows the statistics at the end. -v
would imply -s
, but not vice versa.Does that make sense?
It all makes sense, I can work on that while I'm at it. I propose to open a new task maybe, like Rework -v behavior
or something?
It all makes sense, I can work on that while I'm at it. I propose to open a new task maybe, like
Rework -v behavior
or something?
task? is that a github concept? by all means
With this commit, one must set casync log level to debug in order to see each downloaded chunks (additionally to setting the verbose flag).
Signed-off-by: Arnaud Rebillout arnaud.rebillout@collabora.com