On May 14, 2015, at 11:02 PM, Andy Goth <andrew.m.g...@gmail.com> wrote: > >> On May 7, 2015, at 6:21 PM, Andy Goth <andrew.m.g...@gmail.com> wrote: >>> extra level of reporting > > I made it standard in [fossil changes] and [fossil status]. See commit > [03679b58]. Please give it a whirl and let me know if it satisfies.
I remain unsatisfied and demand a refund for this change in recompense. :) I went digging into the timeline to see why it appeared to do nothing, and found “This change does not apply to Windows.” That’s the only time I really had a problem with this Fossil behavior, as mentioned in the message you quoted. I think this change should at least apply to the Cygwin case, since Cygwin also cares about the executable bit and knows symlinks. As for the native Windows case, I don’t have anything better to suggest for that case than just trying to ignore its existence. :) > Discovered a side effect. This reduces the need for the -allow-empty > option to [fossil commit] since it is now aware of execute and symlink > changes. Nice! I never liked that flag anyway. Maybe it can be de-documented, then maybe later obsoleted, then removed? A bare “fossil ci” should always notice all relevant changes; it should never have to be forced. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
