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

Re: Local changes to externals (Was: Removing externals)

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 06 May 2011 19:32:27 +0200

On 06.05.2011 09:02, Hans-Emil Skogh wrote:
>>>> It ignores *local* changes to the svn:externals property by
>>>> default now.
>>> Oh! I think this is pretty bad. It really flies in the face of
>>> all test-before-you-commit practices. :-( Is there any way we can
>>> improve this on the TSVN-side? Either by making an update always
>>> honor the current WC state of all svn:externals properties (my
>>> preference), or by adding a checkbox to the edit svn:externals
>>> dialog that does the update automatically if the external is
>>> changed (hopefully default-checked..).
>> I'll add an option to change the default.
> Ok, the best we can do I suppose...
>> The current default is what the CL client will use as its default
>> too, because checking for local mods to external props takes a long
>> time and this was done for performance reasons.
> Ouch! I see what you mean. The properties are stored as a single
> string-blob for each node. What a design fail! :-(
> This makes me so sad indeed... So much for a faster working copy
> code; even being forced to make a behavioral change (strictly for the
> worse) because of the bad performance of WC-NG..! *sigh*

If you have a better idea for the design, just mention it on the svn dev
list :)


   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 2011-05-06 19:32:34 CEST

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

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