admin wrote:I could do that, and it would be okay (performance-wise) after a "Merge Folders" prompt. However, if I do it for all folders in the job (also when there is no "Merge Folders" prompt because it's turned off) then it would slow down the process too much.
Therefore, for consistency, I'd rather don't do it at all.
I made some tests and this is totally fast, no performance hit at all.
So it could be done. Question is: Is it okay to "Sync Caps" in all target folders? All the rules we have, like "Overwrite if Newer", only concern files, not folders. So I have nothing to decide which folders should be caps-synced and which not. So it would be all or none. (Unless we have "Ask before merging folders" ON and the answer is "no" -- in that case the caps should not be synced for this branch.)
Generally I agree with you that sync caps is an expected outcome of a sync operation (and probably also of a backup and copy operation). So I'm inclined to do it:
"Sync Caps" in all target folders (apart where merging was explicitly denied by the user) for Copy, Backup, and Sync.
Any objections?