takeshin wrote:
Hi, I have following PHPDoc code in files of my repository: /** * Class description * @version 1.2 */ class Name… Is there a chance that git could increment this @version automatically on each commit
No, but see GIT-VERSION-GEN and "git help describe" for info on how to replace such version tags using a script when you cut a release of your project.
or stamp the file somehow?
Yes. It can only do so using the blob id though. Things like this can be done in CVS and Subversion because a) CVS and SVN are file-based. The version they write are not the version of the *project*, but the version of the file (not even remotely the same thing). b) they do not really support proper branching. In git (which is snapshot based and supports branching very well indeed), it *could* be done, but it would incur such an enormous performance penalty when switching branches, creating a new commit or re-writing history (since every file would have to be altered) that it's never been considered worth adding. -- Andreas Ericsson andreas.ericsson@xxxxxx OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Register now for Nordic Meet on Nagios, June 3-4 in Stockholm http://nordicmeetonnagios.op5.org/ Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- 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