On Wed, Sep 9, 2015 at 10:16 AM, Scott Doctor <sc...@scottdoctor.com> wrote: > > Why does Fossil use a hash for an entries identity instead of sequential > numbering? Seems simply using the rowid of the associated database table > would be more meaningful and practical than those long strings of arbitrary > numbers. >
Some DVCS, like hg, use both an hash and a sequential number. The latter is simpler to keep things locally, but the hash is used when things get distributed to the outside world. So, in the last, you need a UUID or something alike for your repository to be connect-able to other repositories. Luca _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
