2015-04-25 22:54 GMT+02:00 Richard Hipp <d...@sqlite.org>: > On 4/25/15, Jan Nijtmans <jan.nijtm...@gmail.com> wrote: >> 2015-04-25 18:38 GMT+02:00 Andy Bradford: >> So, let's start testing: >> <https://www.fossil-scm.org/index.html/info/560483f50436c9f7> > > The "fossil forks" command applied to SQLite reports these four > check-ins as forks: > > https://www.sqlite.org/src/timeline?c=763d2bc74b&unhide > https://www.sqlite.org/src/timeline?c=7d445e593a&unhide
Those are two tips, both originating from trunk, which both has the same branch-name. Although not exactly matching the definition of fork, they should have been closed before unhiding. So, yes, they indicate a potential problem, I would like "fossil forks" to report this. Remedy: both of those leaves should be closed. > https://www.sqlite.org/src/timeline?c=cbea02d938&unhide > https://www.sqlite.org/src/timeline?c=bf6ca21b36&unhide The same here: there are two tips with branch-name "branch-3.7.16" which forked off trunk. Although not matching the definition of fork, it's a potential problem which I would like to be reported by "fossil forks". Remedy: close at least the second one (but the first one probably as well) Regards, Jan Nijtmans _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
