+1. Been there, two times just in the last week (I need to sleep better). On Thu, May 7, 2015 at 7:51 PM, Andy Goth <andrew.m.g...@gmail.com> wrote:
> I propose extending [fossil changes] to report when a file's execute bit > has changed or it has become a symlink or ceased to be a symlink. > > For various annoying reasons, many times I've unwittingly checked in a > bunch of execute or symlink brokenness, sometimes not discovering it > until much later. Running [fossil changes] before [fossil commit] isn't > enough to protect me from this problem. > > 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. > > -- > Andy Goth | <andrew.m.goth/at/gmail/dot/com> > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
