> Option 1 is to, given the appropriate checkout option, omit the text
> base and instead store a checksum of the working copy file (after
This is my favoured approach. With one slight modification. I think it
should be possible for the repository manager to be able to make this
decision for the users, or at the very least, set the default. What
I'd like to be able to do is some sort of svnadmin command that sets
the policy for all my developers. If an individual developer knows
they will be working offline, then they can over-ride the default
with an svn checkout option. It works in the other direction as well.
If the default is set to USE local cached stored, then the developer
should be able to tell the checkout not to.
In order to achieve this (and I really don't mind contributing
coding cycles to make this happen) I will need to know if there is an
appropriate place to store tree-wide parameters that are set either
at creation time, or modified after the fact. Some sort of internal
svn attributes database. Although I don't know this, I am guessing
that there must be a file somewhere whose properties we can use
for this purpose. However, I think that this should be a setting that
reflects the decision *TODAY*. IE the setting is NOT revision
controlled. I think it has little meaning to apply a decision that may
have been valid 5 years ago, when you pull the tree from 5 years
ago today.
Kean
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 25 21:56:00 2002