On 5/15/15, Warren Young <w...@etr-usa.com> wrote: >> 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.
The whole purpose of --allow-empty is to force Fossil to do a check-in that deliberately has no changes from the previous check-in. This is done, for example, to tag a release. (See https://www.fossil-scm.org/fossil/info/002580c50d94790a). Some people also do it to start a new branch. The --allow-empty flag was never intended to work around failures to detect changes in file meta-data. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
