SteveKing wrote:
> - yes, working copies can be used by more than one user. But why would
> that be a problem for server configs? I mean those configs are intended
> to pass configurations/other information from the server to *all*
> working copies (not just individual users). So a working copy used by
> several people shouldn't be a problem?
Greg is saying that _I_ checked out the WC, and got the server config
files in my .subversion directory. Then _you_ accessed the shared WC
and did something that requires the server config files, but you never
got them. It's not a critical error because in many cases, the server
could signal that your user was not using the latest server config
files, so your commit would fail with an out of date error (and you
could 'svn up' to get the server config in your .subversion directory).
The problem case is that with revert, you couldn't do this (since
revert specifically doesn't require contacting the server).
> by the user perhaps), and a 'revert' would therefore not make much
> sense. I think of such server configs like changes you get when you do
> an 'svn update' - and you can'r 'svn revert' such changes either. You'd
> have to do a merge to get rid of such changes.
If the server config included a custom keyword, the client cannot
perform the revert correctly without having that information (since the
unexpand/expand would need to know about the new keyword). There are
probably other cases where the revert requires having the server config
information in order to restore the file to the original form.
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
Received on Fri Apr 29 20:53:03 2005