Re: [POST 1.0 task] Custom Keywords - Issue 890

Greg Hudson wrote:

> Because of that, it
> makes the most sense to limit repository-based configuration to things
> which talk about the repository's content. Custom keywords definitely
> fit in that category.

That's why I said "to some extent" parenthetically. I agree fully that only
certain values would make sense to support in a repository config file.

> I think it may make more sense to flesh out properties than it would to
> create a new framework for configuration. Some ideas:

[good suggestions]

That was the direction I was thinking would be the most profitable, too.

>
>
>>4) Overrideable by the local .subversion/config or...
>
>
> Why? Give a specific example of something which genuinely belongs in
> per-repository configuration for which there is a legitimate need for a
> client-level override.
>

Sitewide the $Id: $ string could be "%b %r %d %a" (using the notation that epg
suggested), but that may annoy me, and I only want to see "%b %r". It's a weak
example, but if we are already implementing a hierarchy of config settings, it
seems worthwhile to continue up to the user config. It's not as strong a
requirement as the other three, but I don't want to assume I know everything
about how users's might want to use this feature. ;~)

John

-- 
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