Karl Fogel <kfogel@newton.ch.collab.net> writes:
> Why not just write "Maintainer: John Foo" directly in the file? :-)
>
> In other words, I don't see how this idea really makes keywords any
> more powerful. If you have to maintain the property's value, you
> might as well just dispense with the property and maintain a bit of
> text in the file.
Not quite. One of the things i thought of for the keyword format
string was a %k specifer, which would expand to a keyword.
Here's an example:
# Something like this in some repo-side conf file:
[custom keywords]
keyword NetBSD = "%n %r %d %a"
keyword BuildStatus = "%r %k(netbsd:build-status)"
Set the svn:keywords property on your file to 'NetBSD
BuildStatus' and check it in. As different versions of this file
on different branches are auto-built, the BuildStatus will change
(if you have your build scripts set the netbsd:build-status
property).
/*
$NetBSD: foo.c 270 2002-09-02 02:23:31Z epg $
$BuildStatus: 270 failed $
*/
or
/*
$NetBSD: foo.c 261 2002-08-02 02:23:31Z epg $
$BuildStatus: 261 success $
*/
Now i can tell by looking in the nightly tar file whether it
successfully built or not. I can think of plenty other uses for
such a feature, i'm sure.
--
Eric Gillespie <*> epg@pretzelnet.org
Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 5 18:15:40 2002