[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:keyword causes modified status after checkout

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-08-06 21:47:39 CEST

On 05.08.2005, at 00:23, T E Schmitz wrote:

> T E Schmitz wrote:
>
>> Occurrences of $Rev: xxxx $ do not cause this problem, nor does
>> $Revision: $
>
> I just did a test:
>
> It doesn't make a difference whether Rev, Revision or
> LastChangedRevesion are used. What makes a difference is whether
> there is a space after the colon:
>
> $Rev:$
> $Revision:$
> $LastChangedRevision:$
>
> all have the effects described earlier.
>
> $Rev: $
> $Revision: $
> $LastChangedRevision: $
>
> If there is a space after the colon, everything behaves as it should.

I haven't used Subversion keywords so I can't say how it's intended
to work, but the docs [1] imply that the correct way to write an
unexpanded keyword into files is without colon or space after the
keyword name, i.e. just $Rev$

And it clearly works with a space and stuff after the colon (as it
would be if it were expanded). My naïve opinion is that it seems to
me like it would be reasonable for it to work with $Rev:$ too. Bug?
Opinions?

[1] http://svnbook.red-bean.com/nightly/en/
svn.advanced.props.html#svn.advanced.props.special.keywords

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 6 21:49:32 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.