Wayne Davison

Did you test the latest git source? Why are you running -vvv? For a lot of verbosity, it's good to use `--stderr=all` (aka `--msgs2stderr`).

There's nothing wrong with the info_verbosity setup -- it has a defined size to make it the same as the debug_verbosity array, so the unmentioned initializers are all NULL (since...

The uninitialized error is a bit weird. It points to: `if (iobuf.in_fd >= 0 && FD_ISSET(iobuf.in_fd, &r_fds)) {` which I thought shouldn't have any uninitialized memory because `FD_CLEAR(&r_fds)` was called...

I'll note that fixing this is not a very high priority given the better `-ii` option choice & `--msgs2stderr`. Especially since the only things that can really be done in...

I won't be making any statically linked binaries available in order to make sure that we are on the right side of any license issues distributing openssl crypto & xxhash...

I wrote up some package details in the latest INSTALL.md file. You can see the html version here: https://download.samba.org/pub/rsync/INSTALL If folks have hints for other OSes, let me know.

I'd suggest that you find the files you want to send using "find" and then send them using a --files-from list.

Rsync executes its actions in a pipeline of data, so the messages about what files are done are often delayed behind copious amounts of checksum data that is also making...

You don't mention what the failure is. However, I'd guess that it does nothing due to you putting a space after the `--include=` which is telling rsync to include nothing...

Because the sender couldn't open the file, it didn't make it into the file list, so it was not counted at all. So, all those numbers are correct, there's just...