Karl Fogel wrote:
>cmpilato@collab.net writes:
>
>>Yeah, see the problem here is that you set your format string property
>>on trunk. But what if I only check out some sub-tree under trunk?
>>This scenario will inevitably lead to setting your format string
>>property on every directory (since you don't know what portion of the
>>tree folks will check out). But if you're going to be setting the
>>same property so many times, why not set it instead only the files
>>that want to expand it?
>>
>
>But maybe the format strings could be configured in some text file in
>the repository (I mean "in the repository" in the sense that the hook
>scripts are in the repository), and the client would fetch that file.
>That way, the custom keywords would be global to that repository,
>which matches the administrative boundaries that exist in real life.
>
Right. Hm. On the one hand, you'd want the format strings to be global
to the repository. On the other hand, you want them versioned. The
notion of "repository properties" comes to mind. They'd be versioned
like node properties, but apply to the whole repository, and accessible
through any node. Say in the "svn:repo:" namespace.
It's a pity they'd play havoc with the way we handle properties in the
WC ATM ...
Just thinking out loud.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 3 15:15:32 2002