Return to Question

For rsyncs that involve a large number of potentially transferred files, I mean to have a "clean" log, with only what was transferred. I worked with stdout, since: 1) I did not know how to configure the log output (if that is even possible). I had yet another reason forcing me to work with stdout, with something like this, since: 2) I also want this to work with --dry-run. And perhaps yet another reason: 3) I mean to write scripts useful for transferring Linux-Linux, and Linux-msys2 (and viceversa) at least. Here, options for permissions (-p), owner (-o) and group (-g) may complicate things.

For rsyncs that involve a large number of potentially transferred files, I mean to have a "clean" log, with only what was transferred. 

I worked with stdout, since:

1. I did not know how to configure the log output (if that is even possible).
2. I also want this to work with --dry-run (which forced me to work with something like this, since).
3. I mean to write scripts useful for transferring Linux-Linux, and Linux-msys2 (and viceversa) at least. Here, options for permissions (-p), owner (-o) and group (-g) may complicate things.

Note: The subtleties in this question (see also answer) make it slightly different from other similar questions posted/linked. Whether this warrants a separate question is a blurred line, and subjective. I personally find it useful to leave it as it is now.