Re: On making times=true the default

--===============3042084159023894683==
Content-Type: multipart/alternative; boundary="00000000000060091e062bd8b892"

--00000000000060091e062bd8b892
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I may be being overly cautious here. I certainly use -times=3Dtrue myself.

As for history, I'm not sure there was a very strongly reasoned reason for
the default setting being false.  It's possible that flag was added
sometime after the initial system was deployed and we were already feeling
cautious about not disrupting people's expectations.



On Thu, Jan 16, 2025 at 3:28=E2=80=AFPM Greg Troxel <[email protected]> wrote:

> Benjamin Pierce <[email protected]> writes:
>
> > FWIW, I'm a little nervous about changing defaults on something so
> > fundamental.
> >
> > E.g., we can be careful not to do it when using old archives where time=
s
> > have not been synced, but what if those archives get blown away and the
> > user expects to be able to just run unison again to recreate them from
> > scratch?  This is something some people might be quite surprised by.
>
> Assuming we can implement automatic merge to older mtime, what are you
> concerned about in terms of semantics and user expectations?
>
> Do you think someone is relying on the mtimes of a replica where unison
> rwote the file (as opposed to the user) being the time that it was
> synced, instead of the most recent non-sync change?
>
> If you do believe that people that want this exist, do you think they
> are more than a tiny minority?   Would they be adequately served by a
> caution in NEWS to set --times=3Dfalse, to get this old semantics?
>
> (I view lack of syncing mtimes as a bug, and I am guessing it was
> inspired by Windows trouble.  But a historical perspective might be
> helpful.)
>
>

--00000000000060091e062bd8b892
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">I may be being overly cautious here. I ce=
rtainly use -times=3Dtrue myself. =C2=A0<div><br></div><div>As for history,=
 I&#39;m not sure there was a very strongly reasoned reason for the default=
 setting being false.=C2=A0 It&#39;s possible that flag was added sometime =
after the initial system was deployed and we were already feeling cautious=
=C2=A0about not disrupting people&#39;s expectations.</div><div><br></div><=
div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Thu, Jan 16, 2025 at 3:28=E2=80=AFPM Greg Troxel &lt;<a =
href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(2=
04,204,204);padding-left:1ex">Benjamin Pierce &lt;<a href=3D"mailto:bcpierc=
[email protected]" target=3D"_blank">[email protected]</a>&gt; writes:<b=
r>
<br>
&gt; FWIW, I&#39;m a little nervous about changing defaults on something so=
<br>
&gt; fundamental.<br>
&gt;<br>
&gt; E.g., we can be careful not to do it when using old archives where tim=
es<br>
&gt; have not been synced, but what if those archives get blown away and th=
e<br>
&gt; user expects to be able to just run unison again to recreate them from=
<br>
&gt; scratch?=C2=A0 This is something some people might be quite surprised =
by.<br>
<br>
Assuming we can implement automatic merge to older mtime, what are you<br>
concerned about in terms of semantics and user expectations?<br>
<br>
Do you think someone is relying on the mtimes of a replica where unison<br>
rwote the file (as opposed to the user) being the time that it was<br>
synced, instead of the most recent non-sync change?<br>
<br>
If you do believe that people that want this exist, do you think they<br>
are more than a tiny minority?=C2=A0 =C2=A0Would they be adequately served =
by a<br>
caution in NEWS to set --times=3Dfalse, to get this old semantics?<br>
<br>
(I view lack of syncing mtimes as a bug, and I am guessing it was<br>
inspired by Windows trouble.=C2=A0 But a historical perspective might be<br=
>
helpful.)<br>
<br>
</blockquote></div>
</div>

--00000000000060091e062bd8b892--

--===============3042084159023894683==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Unison-hackers mailing list
[email protected]
https://LISTS.SEAS.UPENN.EDU/mailman/listinfo/unison-hackers

--===============3042084159023894683==--