https://bugzilla.samba.org/show_bug.cgi?id=14371
--- Comment #7 from Wayne Davison ---
If you don't want something deleted on the receiving side, you need to protect
it via either a protect rule or an exclude rule. Using --delete-excluded just
turns all exclude rules into hide rules, which
https://bugzilla.samba.org/show_bug.cgi?id=14371
Wayne Davison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugzilla.samba.org/show_bug.cgi?id=14371
Haravikk changed:
What|Removed |Added
Resolution|WONTFIX |---
Status|RESOLVED
https://bugzilla.samba.org/show_bug.cgi?id=14371
--- Comment #5 from Haravikk ---
Oh, I see; so hide actually does what I need, you confused me with the mention
of not using --delete-excluded, as it actually seems to work just fine with a
mixture of hide and exclude rules for different items.
https://bugzilla.samba.org/show_bug.cgi?id=14371
--- Comment #4 from Wayne Davison ---
You don't add an exclude rule, you add a hide rule. An exclude rule is a
combination of a hide (server side) and a protect (client side). So you choose
between the 3 idioms (hide, protect, exclude) depending
https://bugzilla.samba.org/show_bug.cgi?id=14371
--- Comment #3 from Haravikk ---
If I remove --delete-excluded then how do I ensure my backups remove items
matching new exclusion rules? For example, if I identify a new cache folder or
such that I don't want to copy, and it add to my exclusion
https://bugzilla.samba.org/show_bug.cgi?id=14371
Wayne Davison changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=14371
Wayne Davison changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
