2015-03-20 4:56 GMT+01:00 Richard Hipp <d...@sqlite.org>:
> I rue the day that I allowed that patch to land on trunk.
> But it is all fixed now - you won't have the problem with 1.32.
Note that the "initial empty commit" is an unique feature of
fossil, GIT and SVN don't have that. Abilio started with
a completely empty repository and started committing from
two different (empty) checkouts. That means the two
file sets committed don't have any relation. If you
use fossil 1.32 for doing the same, there will be
an additional initial empty commit, which suggests a
relation which isn't really there. The only problem
I see in your workflow is that you were not warned
that actually you were creating a fork, in 1.32 you
will get that warning (after doing the same steps):
$ fossil commit -m "commit b"
would fork. "update" first or use --allow-fork.
Thank you for your report.
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
