On the sending folder override means tramp anyone elses changes, even if changes on the receive only are not actual changes that are propagated, it just propagates that it does not have the file because it modified it.
You want to revert local changes on the receive only folder.
Override changes on send only promotes it’s local view as the global view which is what all devices aim to get to. Remote side can still choose to ignore it (because it’s send only, or it’s receive only with local modifications which would be tramped if it were to follow them).
Revert local changes on receive only reverts any local changes, which are in conflict with the global view, which as a result prevent it from achieving the global view (as you’d lose local modifications).
The changes are on the “receive” side, and conflict with incoming files.
Say I change a file, locally, on the “receive only” side, but I WANT the version of the “send only” side to overwrite it, regardless of date/status, would I choose override or revert?
(Note, versioning is on, so the overwritten version will of course be moved to .stversions regardless
(EDIT: Assume all changes on “receive” side are accidental, if that helps for this example)
You’d choose to revert, as I’ve explained, override just suggests what the state should look like, it does not mean others will accept it, and in this case they won’t, as that would mean data loss of the local changes.
It seems backwards to me. To someone unfamiliar with the whole thing, “override” seems like it MIGHT mean “override remote file version conflict warnings and push the file.” Which it apparently does not mean.