Andy Parkins wrote: > What about this though: > * Tag a release > * Export the working tree into a fresh directory > * Edit each source file to put the hash of the tagged revision into > every file. > * Edit the makefile to include the tag hash in the released version > * tar it up > * Release > It's such a mundane, useless waste of time to edit the hash in by hand - why > can't the version control system do it? What about this (that is roughtly what git and Linux kernel use): * Tag a release * Issue "make dist" which would automatically replace @@STH_VERSION@@ (or ++STH_VERSION++ for example in Perl files) with result of "git describe" (although I think that plain old "make" also does this) _and_ create proper STH_VERSION file * tar it up using "git archive --format=tar" which would add version as a tar comment * Release -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - 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