On Tue, 17 Jul 2007, Shawn O. Pearce wrote:
The first fixes the -dirty build problem. The second drops off the extra information that git-describe throws into the mix when it generates output for a non-tagged commit. The third kills the rc* component if this is a release candidate. Note that the rc* killer must come after the git-describe killer, as the rc* part is actually in the real tag. The last one fixes the weird case where the user has somehow bungled his git software distribution so it cannot generate a git version via git-describe *and* they have no `version` file in the source code directory. Such people really should fix their git. But anyway we do support it now.
Well, I would say that my git is not broken, but simply temporary. I have a machine that is not connected to the internet where I want to run git. Normally I use release tarballs, but at the moment I need the recent changes to fast-import, so I am running whatever was master at the time I made the tarball.
As soon as 1.5.3 comes out I will be back to using the official releases. I just wanted to run git-gui blame (a rather nice tool) to look at what the result of my latest test import looked like. Since I wasn't using git for anything other than playing with fast-import, creating a properly versioned git seemed like more effort than it was worth.
-- Julian --- The major difference between bonds and bond traders is that the bonds will eventually mature. - 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
