On So, 18 Okt 2009, demerphq wrote: > > Being a DVCS, this kind of versioning can only be trusted on a single repo, > > but if you set it on the "main" repo, it should work. > > > > The only drawback could be the ever growing number of tags, > > I don't know how it will work with thousands of tags or more. > > I think the other drawback is that the number would essentially be > meaningless and more or less would just be a substitute sha1. Well, it would be increasing for that repository. And if we always update our packages from that repository the packages will be guaranteed to have increasing version number, too. That is the *only* thing I care about. The numbers don't need to have a meaning, nothing else but that in our workflow we guarantee that at the end each package progresses in version numbers. > Consider when a remote adds commits and then merges and pushes. What > number should those commits have? When using a central repository to which he pushes within that central repository it would give a specific number. Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining Associate Professor JAIST Japan Advanced Institute of Science and Technology preining@xxxxxxxxxxx Vienna University of Technology preining@xxxxxxxx Debian Developer (Debian TeX Task Force) preining@xxxxxxxxxx gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- WIMBLEDON (n.) That last drop which, no matter how much you shake it, always goes down your trouser leg. --- Douglas Adams, The Meaning of Liff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html