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

Re: TortoiseSVN-1.5.0-RC2 released

From: Ed Avis <eda_at_waniasset.com>
Date: Wed, 21 May 2008 13:06:24 +0000 (UTC)

Andy Levy <andy.levy@...> writes:

>>Upgrading the working copy makes it
>>incompatible with the current stable TortoiseSVN release.
>One can only install one version of TSVN on a given system in the
>first place (aside from maybe Win32 & Win64, in which case most people
>already know what they're doing). So wouldn't this be moot anyway,
>unless you're sharing a WC with multiple clients PCs/users, which you
>aren't supposed to be doing in the first place?

I must admit I'm doing that, whether supposed to or not. We keep some
configuration files in svn, and to make changes you check in your change and
then 'update' in the config directory. So the config directory is itself a
working copy, which a handful of different users have access to. If ad hoc
configuration changes need to be made directly, this can happen and then they
can be checked in or reverted later.

Is there a recommended way to keep configuration files in svn and still have the
convenience offered by TortoiseSVN of one-click update or diffing?

Ed Avis <eda_at_waniasset.com>
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-21 15:06:50 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

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