--- Comment #3 from Urban Mueller <> ---
Thanks for the fix, that will solve my problem. However I think the planned -c
behaviour is surprising in a bad way. If rsync has a way to achieve its desired
target state, IMHO it should. Example: If the target directory is writable but
contains a file owned by root with mode 600 (ie not writable by normal users),
rsync -ac will happily replace it if a normal user transfers a file with the
same name. However if the file has a nearly identical time stamp and is
otherwise identical with the source, he suddenly gets a warning every time he
tries to copy?

You are receiving this mail because:
You are the QA Contact for the bug.

Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
Before posting, read:

Reply via email to