On Fri, Aug 28, 2009 at 12:45, Yves Goergen<nospam.list_at_unclassified.de> wrote:
> On 28.08.2009 08:11 CE(S)T, Yves Goergen wrote:
>> No, the "$Revision$" is of course not in effective source code as it
>> would be totally in the way there. It's just in a // comment line so the
>> compiler won't ever see that information. My script just tries to grab
>> it from that line and copy the bare number into the active code line so
>> that it can compile. The repository always has the version number
>> "x.x.x.0" in that place, so if you won't use the script, you just won't
>> have the revision number in the code, that's all.
>
> Hm, as I had to find out today, it doesn't quite work. The file
> AssemblyInfo.cs is actually never changed an so the keyword substitution
> is never updated. So it is stuck on some revision from the past.
>
> Is that by intent that keywords are not updated if the file didn't
> change? How is something like $Revision$ meant to be useful if it
> doesn't reflect the revision?!
$Revision$ reflects that last revision in which *that file* changed.
It's very useful for keeping track of individual source files.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2388330
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-28 18:49:19 CEST