Karl Fogel <kfogel@newton.ch.collab.net> writes:
> Yeah. We had some proposals for a super-sophisticated keyword "alias"
> mechanism, where people could define custom combination keywords. But
> it was never clear where the mapping would be stored (or maybe I'm
> just not remembering the proposals well enough?)
I proposed a format string solution, but didn't know enough about
svn to comment on implementation details. Now i know a bit more,
and have an idea: put the information in directory properties.
For example, if svn:keywords lists an unknown keyword 'foo' check
for the presence of a property custom-keyword:foo on the current
directory and keep climbing up the directory tree until you find
one. If you don't find one, don't expand it, if you do, expand it
to the string specified there, replacing format specifiers.
So i could set svn:keywords to 'Progeny' on all the files we modify
and set custom-keyword:Progeny to '%f %r %d %a' on /trunk. %f is
base filename (which svn doesn't currently support but should), %r
is revision, %d is date, and %a is author.
That's just one way to do it with properties. I'm not sure it's
the best way or even if it's possible (i know little about the
implementation of properties), but i do think properties would be
a good way to accomplish it.
--
Eric Gillespie <*> epg@pretzelnet.org
Conformity is a sin.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 3 05:19:11 2002