On Thu, Sep 10, 2015 at 9:29 AM, Michal Suchanek <hramr...@gmail.com> wrote: > Given that fossil does not support history rewriting by design the > commit number on a particular branch counting from root is unique and > stable per branch across all repos. > > If you release from a single master branch you have a monotonous > snapshot number. > > When you use multiple branches you need to add branch name to have > stable unique identifier. > > This is not viable eg. for git with rebasing.
I think (accidental) forks in fossil would also break the uniqueness of the numbering scheme. For example see figure 3 of http://fossil-scm.org/xfer/doc/trunk/www/branching.wiki Both check-ins 3 and 4 are equidistant from the root. More complicated cases with differing numbers of check-ins on each side of the fork are possible. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
