From: David Kastrup Date: Fri, 27 Jul 2007 07:42:03 GMT Subject: Re: git-gui problem with version number. Message-ID: <86k5smnvhw.fsf@lola.quinscape.zz> In-Reply-To: <85ejiu5r9r.fsf@lola.goethe.zz> David Kastrup writes: > "Shawn O. Pearce" writes: > >> David Kastrup wrote: >>> "Shawn O. Pearce" writes: >>> > Anyway, you can setup a build with the most recent 'stable >>> > development' version of git-gui: >>> > >>> > git checkout -b with-new-gitgui >>> > git pull -s subtree git://repo.or.cz/git-gui.git >>> >>> Ok. Would the necessity for this depend on the Tcl version? >> >> I thought all versions of Tcl did not understand the 'creative' >> git version strings. So I'm surprised to hear it works on one >> system but not on another, even though you have the same version >> of git and git-gui. > > I'll check once I am at work, but I am pretty sure that the versions > are pretty much in synch. Now that is funny. I am pretty sure (or rather _have_ been pretty sure) that I cloned the respective repositories with the same command. Yet now both are up-to-date according to git-pull (and have identical .config contents), and the first compiles version git version 1.5.3.rc2.41.gb47b1 while the second compiles version 1.5.3.rc3.7.gd58e-dirty. Both have been cloned from git.git, the second with * master origin/HEAD origin/html origin/maint origin/man origin/master origin/next origin/pu origin/todo and the first with * master origin/HEAD origin/html origin/maint origin/man origin/master origin/next origin/pu origin/todo On the one with the problematic version, I get git-rev-list -2 origin/HEAD |git-name-rev --stdin d58e8d34b019d435b424811c6f972910dfac6f55 (master) 1a44be9a0ff6fa623ff6061992f5ad1831dc7cab (master~1) and on the other one I get git-rev-list -2 origin/HEAD |git-name-rev --stdin d58e8d34b019d435b424811c6f972910dfac6f55 (remotes/origin/HEAD) 1a44be9a0ff6fa623ff6061992f5ad1831dc7cab (remotes/origin/HEAD~1) git-rev-list -2 master |git-name-rev --stdin 0d59d6cfd3ed2510a8e7d8c9fbc54c21133bc3a6 (master) d58e8d34b019d435b424811c6f972910dfac6f55 (remotes/origin/HEAD) So let me guess: the "dirty" in the version number comes about when one has changes that are not in the upstream version, and it is this string which confuses git-gui? But then the version numbers are _so_ different. I probably am overlooking something. -- David Kastrup