Re: Unison improper behaviour on metadata change (chmod and chown) with force=newer.

Tõivo Leedjärv <[email protected]> writes:

> On Fri, 29 Sept 2023 at 19:19, Greg Troxel <[email protected]> wrote:
>>
>> I think my suggestion is consistent with yours, except that I don't see
>> it as reasonable to do any kind of force if the two mtimes are the same.
>
> Yes, completely consistent. My suggestion is, using other wording,
> exactly like you said: if mtimes are equal then act as if
> force=newer/older was not specified, _with the additional caveat_ that
> in case of a conflict (changes on both sides) force one of the
> replicas (just as is done today).

Not completely consistent: I don't think there should be any forcing.

>> sense of newer for properties.   So just acting like force wasn't
>> enabled seems safe, even if it might be annoying.
>
> Agree. Even if we don't end up doing any code changes, I think this
> caveat deserves a mention in the documentation. force=newer/older is
> only defined for file content changes, it may not work as expected for
> metadata changes and may even revert such changes.

I'd have to read the text, but newer/older means mtime, and it seems
obvious that this means sync everthing with the newer being the source.

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].