Apparently the "automatic fork check" is in trunk. 1) On a large repo, this takes an inordinate amount of time. On a sync (with no updates necessary), the runtime is ~45s (on the first attempt, I stopped it after ~10 mins of running in order to re-run it with a time(1) command to collect info) on a network run that took ~1s.
2) Do we not have a policy yet about dumping unratified code in [trunk] ? If not, I vote "please do not do this" On 4/27/15, Andy Bradford <amb-fos...@bradfords.org> wrote: > Thus said Richard Hipp on Sun, 26 Apr 2015 18:34:23 -0400: > >> The "forks" query parameter to the /timeline page now shows recent >> forks in the check-in DAG. For this page, a "fork" means a check-in >> with two or more children in the same branch. No attempt is made to >> distinguish between forks that have been resolved and those that have >> not. > > I like it. Works great here. > > Thanks, > > Andy > -- > TAI64 timestamp: 40000000553e91f0 > > > _______________________________________________ > 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
