[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Pre-Design Discussion of Server->client configuration

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-04-29 20:58:20 CEST

John Peacock wrote:
> 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

Ah, now I get it. Sometimes I'm a little slow ;)

[snip]
> 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.

Ok, then a problem with 'revert' would only apply to the also to be
discussed feature 'custom keywords'.

Thanks for explaining!

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 29 21:00:08 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.