Another thing that I think it's important is the difference between git and svn is the way you can commit. In svn it's linear, you commit after another commit but in git it's like a tree you can make branches and merge them with the main branch seperately so a number can't be a good way of determination of current version On Jan 15, 2014 11:28 PM, "Merlijn van Deen" <[email protected]> wrote:
> On 15 January 2014 13:47, Bináris <[email protected]> wrote: > >> I am afraid I don't really understand you. >> Was there any real problem with SVN version numbers? >> What kind of local commit? There was one system with one series of >> numbers. Do you mean your own computer by local? That is not interesting >> for public. >> > > Reading a git tutorial (or two) might help to understand the issue. To > help understand the differences from SVN, http://hginit.com/00.html is > really helpful - it's written for mercurial, but you can just read 'git' > everywhere 'hg' or 'mercurial' is used. > > >> The old version number HAD some meaning. It gave a sort order, some help >> where to put a script in my mind. This new system is only useful for >> computers. Well, we can live together with that, but if there is any chance >> to install some human readable version, I would appreciate it. >> > > I have given you the exact command that you can use to get 'a human > readable, incrementing version number'. But I've asked this before, and > I'll ask it again: why do you need a revision number? What is the use case, > and why couldn't that use case also be handled by a revision hash? > > Merlijn > > _______________________________________________ > Pywikipedia-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l > >
_______________________________________________ Pywikipedia-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
