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

Re: Spaces in Keyword Expansion

From: Vincent Lefevre <vincent+svn_at_vinc17.org>
Date: 2005-07-06 18:18:27 CEST

On 2005-07-06 10:08:51 -0400, John Peacock wrote:
> Vincent Lefevre wrote:
> >In particular, how are control characters in filenames handled?
> They aren't [currently] escaped/encoded.
> >Are they encoded? If not, what about the end-of-line characters
> >vs the svn:eol-style property?
> All keywords must be a single line (and placing a EOL character in a
> file name, while technically legal, is a really poor choice).

I know that, but users shouldn't be able to screw up their repository.
One could also say that placing space characters in filenames is a
poor choice (at least, under Unix), though some people do that.

> >And what about the '$' character in a filename, which must not
> >appear inside a keyword expansion?
> Don't do that (including '$' in a filename).

There may be valid reasons to have '$' in a filename (like any other
printable character).

> >Also, when are locales considered for keyword expansion?
> They aren't [currently].

I thought the Date keyword used the locales, or has this changed?

> >How do Subversion developers suggest to parse keywords (in
> >particular, Id)?
> Don't parse it.

AFAIK, this is the only way to get the UTC date (if one wants to avoid
a conversion). Moreover it is easier to use Id than the other keywords
when one wants to get several metadata.

Vincent Lefèvre <vincent_at_vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 6 18:32:44 2005

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

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