Following up on this bug report, does anyone still get this error on
rsync 3.1.1?

If not, I'll mark this bug as fixed in 3.1.1.


Thanks,
Paul

Reply via email to