On 5/15/2015 12:02 AM, Andy Goth wrote: > On 5/8/2015 1:13 PM, Warren Young wrote: >> On May 7, 2015, at 6:21 PM, Andy Goth <andrew.m.g...@gmail.com> wrote: >>> My question is whether this extra level of reporting should be standard >>> [fossil changes] behavior or only accessible if an extra option is >>> supplied. My vote is to make it always report execute bit and symlink >>> state changes. >> >> I’m in favor of the idea, but I’ll tell you this up front: I’ll never >> see the warning unless it appears in either “fossil status” output or >> in the editor text generated by the interactive form of “fossil >> checkin”. I don’t use “fossil changes” at all. Deep svn muscle >> memory keeps me saying “f stat” instead. > > 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.
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. -- Andy Goth | <andrew.m.goth/at/gmail/dot/com>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
