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

Re: Custom keywords, issue #890

From: John Peacock <jpeacock_at_rowman.com>
Date: 2006-09-27 16:30:29 CEST

Garrett Rooney wrote:
> I believe John Peacock was the one originally pushing this work, and
> he got a bunch of groundwork style patches in place, but I haven't
> heard much about it lately, and I'm not sure what the status is.

Actually, Max wound up rewriting my repackaging of plasma's patch to
make keywords into a hash (did you follow that?). What's committed is
the foundation for custom keywords, but unless the OP was talking about
a custom patch to the Subversion source (like BSD initially did with
CVS), until we have a repository-resident configuration, e.g.


there isn't any way to enable custom keywords. It's [relatively]
trivial to add a new keyword as a patch to the core, however that means
that *everyone* who uses that repository needs to apply the patch as well.

I haven't had much brainpower to devote to Subversion hacking for the
last 6 months or so; I don't know if that will change any time soon.
The level of nitpicking^Wreview that went into the "keywords as hash"
patches were quite draining. It's very hard for me to dedicate that
much effort with no guarantee of any resolution.

Honestly, I think that until a core developer (who may very well be paid
to do so) gets interested in developing the server-side config piece, I
don't see any hope for this to go much farther. That feature is going
to need a champion, and frankly, I'm not up for it...


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 27 16:30:45 2006

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.