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>
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
