From: Andreas Ericsson <ae@op5.se>
To: takeshin <admirau@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: update @version in file
Date: Wed, 13 May 2009 11:11:52 +0200 [thread overview]
Message-ID: <4A0A8ED8.8000905@op5.se> (raw)
In-Reply-To: <1242205190383-2879913.post@n2.nabble.com>
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@op5.se
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.
next prev parent reply other threads:[~2009-05-13 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 8:59 update @version in file takeshin
2009-05-13 9:11 ` Andreas Ericsson [this message]
2009-05-13 9:22 ` takeshin
2009-05-13 9:42 ` Jakub Narebski
2009-05-13 16:04 ` Dan Loewenherz
2009-05-13 16:56 ` Jakub Narebski
2009-05-13 17:05 ` Matthieu Moy
2009-05-13 17:38 ` Andreas Ericsson
2009-05-13 23:02 ` Jakub Narebski
2009-05-14 7:08 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A0A8ED8.8000905@op5.se \
--to=ae@op5.se \
--cc=admirau@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).