The "bug" part was working through the assumptions in older code which expected to always have exactly one initial commit. Once those were resolved (largely by Jan), it graduated to a feature.
----- stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Jan 22, 2015 10:11 PM, "Jan Nijtmans" <jan.nijtm...@gmail.com> wrote: > 2015-01-22 17:50 GMT+01:00 Ron W <ronw.m...@gmail.com>: > > So, a "bug" was promoted to a feature? > > Hm, yes, that's one way to look at it. > > Actually, having more than one "initial" commit is not > a bug. The only problem was that the fossil code > assumed in some places that there was only one. > The bug was that fossil mis-behaved when there > were no "initial" commits, and therefore always > created one just to be sure. > > Since fossil 0.30, the initial commit is not special > any more. It's a normal commit which simply has > no ancestors. And all restrictions on how many > of them there should be are gone. It's up to > you how to use that. > > 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 >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
