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

Re: Changed behaviour in handling SVN externals.

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 07 Aug 2009 17:16:13 +0200

On 07.08.2009 15:51, Hans Pabst wrote:
> Hi,
> in previous releases of TortoiseSVN i was able to add an SVN external and *without* committing this SVN property i was able to fetch the external data according to the SVN-external in each case where the repository got updated. This was very helpful and convenient.
> In the current and even the former release this behaviour changed somehow. Now an initial commit of this SVN property needs to happen before fetching the data is possible. This is kind of logically broken from my point of view. It is causing some unwanted commits just to get some data in. I would like to commit only when the property setup is satisfying, settled or tested.
> Now the surprising part is, once an SVN external is commited, any change of this properties (e.g. point to another location) does *not* need a commit before it is possible to fetch the data according to the uncommitted location.
> I suggest restoring the former behaviour here, and thinking through how this is related to other SVN properties and how to handle this in general.

If you want this changed, you have to ask on the Subversion mailing
list. This feature is done by the svn library, not TSVN itself.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-07 17:16:38 CEST

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