David Weintraub wrote:
> On Sat, Oct 25, 2008 at 11:55 PM, Bill Hoffman <bill.hoffman_at_kitware.com> wrote:
>> That is not really what I had in mind. I was thinking that each project
>> could have a config file. Maybe it is a property set on the project.
>> If you could set a property for that project in svn that marked a file in
>> the tree as the config file. Then svn would look at that file for config
>> information. It would always be a file that is on the client. So, the svn
>> command would not have to talk to the server.
>>
>> So, something like this:
>>
>> svn propset config src src/config
>>
>> That would set the config property on the directory src. It would say that
>> in the src tree there is a file located at src/config.
>
> As far as the Subversion client is concerned, each directory in your
> working directory is the root of the Subversion tree. That's why each
> directory has its own .svn file.
OK, so what if the config property was global for a tree. The data for
the config file would be duplicated to all .svn directoires that it was
set on. svn propset config src/config --recurse or something like
that. It would push the config information into all .svn directories
and store the information in the .svn directory of each.
-Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-28 02:27:05 CET