"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > David Kastrup <dak@xxxxxxx> wrote: >> David Kastrup <dak@xxxxxxx> writes: >> >> > 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 >> >> A combination of rebasing and pushing made the difference go away and >> made git-gui work again. Nevertheless, it would be a good idea not to >> balk at the dirty version strings. > > Did you not see me already state in this thread that its already > been fixed? I saw you state that the problem was fixed in your local version, but that this had not been pulled into git.git. So I was adding a vote to have this included. > Latest git-gui already has the problem dealt with, and that latest > version will be included in git 1.5.3 when it ships. That is good to hear but it was far from obvious when I wrote the above mail. > Nevertheless, thanks for the problem report. You are welcome. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum - 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
