On Fri, Mar 4, 2011 at 7:22 AM, Martin Gagnon <[email protected]> wrote: > I've made you test... and after I push from first clone, it give no > error at all like > there's no conflict. But when I look at the main timeline (with fossil ui) > on central, the change from first clone create a new leaf. Without any tag or > branch name.. it fork from previous version into a leaf and both leaf > are in trunk.
So, Fossil automatically creates a new branch with not even an informational message saying it did that? That seems like a bug to me. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
