On Wed, Dec 27, 2017 at 11:56:31PM +0100, Olivier Mascia wrote: > > Le 27 déc. 2017 à 23:24, Joerg Sonnenberger <jo...@bec.de> a écrit : > > > > On Wed, Dec 27, 2017 at 10:10:21PM +0000, bch wrote: > >> On Wed, Dec 27, 2017 at 2:06 PM Olivier Mascia <o...@integral.be> wrote: > >> > >>> Hello, > >>> > >>> Coming from subversion where there is a revision number, incremented by > >>> one by each commit, > >> > >> > >> > >> Let me be the first of many to say that those centrally controlled > >> increments are not possible in a *distributed* source control system. > > > > That's not completely true. You could use the length of the commit chain > > to the root for most of the purposes of the CVS/SVN revision number. > > It's just not necessarily a unique property of a commit. > > Thanks Joerg. > > >> I'm considering replacing the subversion revision ID, for the purpose of > >> defining the file version ID (as above) at release-external build time, by > >> the count of check-ins in the root repository. That is the count returned > >> by 'fossil info' in one of the multiple lines of output (for instance > >> 'check-ins: 8801'). > > My 'count of check-ins' is your 'length of the commit chain to the root', or > are we talking of something else here?
If you have a commit graph like: A | B | \ C D | | E F Both E and F have a LoCC of 4, but the count f check-ins would depend on the order of commits? Joerg _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
