> Le 27 déc. 2017 à 23:10, bch <[email protected]> a écrit : > > On Wed, Dec 27, 2017 at 2:06 PM Olivier Mascia <[email protected]> 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. Maybe a “feature > branch” and your own heuristics would fit the bill?
Brad, I think I know that and wrote it in my message. The question was indeed about my proposed heuristic to use the count of check-ins: > Of course this characteristic (a sequential revision ID) is logical in a > centrally managed system as subversion and is less trivial in distributed scm > like fossil or git. > > 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'). > > The full version string (as "1.2.4.8801") would then be automatically added > as a tag to the most recent check-in on trunk (from which the build is > derived). > > How does that sound to those of you who might have had similar concerns? > Been there and rushed away? Or happy to stay? -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
