git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Creating something like increasing revision numbers

From
Norbert Preining <preining@logic.at>
Date
Oct 18, 2009, 15:20 UTC
Message-ID
<20091018152054.GA3956@gamma.logic.tuwien.ac.at>
In-Reply-To
<200910181703.20607.johan@herland.net>
On So, 18 Okt 2009, Johan Herland wrote:
> A global, increasing version number ala SVN is fundamentally impossible in 
> any distributed version control system (like Git).
Yes, agreed. 

The point is that I do not actually need the "distributed" part of git. I want one central repository and all collaborators commit to that. Yes, that is subversion, I know.

We have no branches, no tags, nothing of that. Only trunk.
Show 5 quoted lines
>     $ git describe
>     v1.0.4-14-g2414721
> 
> where the "v1.0.4" part is the last tag that the current state is based on, 
> the "14" part is the number of commit between that tag and the current 

So if we have only one tag (initial) then it would count the number of commits?

And if yes, is it easy to find out at which commit a file has been changed last time (svn status -v).

I have read a lot on the net about the impossibility, and I agree that in a distributed setting it does not work.

And in fact we would not even have revision numbers on our local git repositories. Only one (the master checkout from which our distribution server is updated) needs to have some commit numbers.

THe reason is that we use that as serial number for packages. One packages is roughly on package from CTAN (Comprehensive TeX Archive Network, like CPAN), and we want to make sure that if that is updated on CTAN and we import it into our system, the next time we create a TeX Live package for it (that will be served to quite a lot of users) we have a new version number.

We first thought about using the version number as provided by authors, but that is completely useless, because there are tooo many authors of packages on CTAN where the version numbers are in no way increasing ;-) So we settled for the max of all the last changed revision number of the contained files, whcih is guaranteed to increase.

As a lat resort I will try to use git-svn ...
Again, thanks a lot and all the best
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining                                        Associate Professor
JAIST Japan Advanced Institute of Science and Technology   preining@jaist.ac.jp
Vienna University of Technology                               preining@logic.at
Debian Developer (Debian TeX Task Force)                    preining@debian.org
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
QUOYNESS (n.)
The hatefulness of words like 'relionus' and 'easiephit'.
			--- Douglas Adams, The Meaning of Liff
Previous: Johan HerlandNext: Johan Herland
Message 3 of 23 in “Creating something like increasing revision numbers”
  1. Norbert PreiningOct 18, 2009
  2. Johan HerlandOct 18, 2009
  3. Norbert PreiningOct 18, 2009
  4. Johan HerlandOct 18, 2009
  5. alexandrulOct 18, 2009
  6. Nicolas PitreOct 19, 2009
  7. Junio C HamanoOct 18, 2009
  8. Norbert PreiningOct 19, 2009
  9. alexandrulOct 18, 2009
  10. demerphqOct 18, 2009
  11. Norbert PreiningOct 18, 2009
  12. demerphqOct 18, 2009
  13. alexandrulOct 18, 2009
  14. Jon SmirlOct 18, 2009
  15. Daniel BarkalowOct 18, 2009
  16. Norbert PreiningOct 19, 2009
  17. Daniel BarkalowOct 19, 2009
  18. Norbert PreiningOct 19, 2009
  19. Daniel BarkalowOct 19, 2009
  20. Nicolas PitreOct 19, 2009
  21. Norbert PreiningOct 19, 2009
  22. Johannes SixtOct 19, 2009
  23. David AguilarOct 21, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.