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

Re: Externals and repository update checking

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 7 Apr 2011 16:19:30 +0200

On Wed, Apr 6, 2011 at 13:27, Hutchinson, Steve (UK)
<steven.hutchinson_at_mbda-systems.com> wrote:
> Hi,
> Have a product structure that look like the below :-
> -------Module A
> -------Module B
> -------Module C
> -------Module D
> The DESIGN_FOLDER has external properties to import say Modules A and B into
> the design folder. The external specifies a specific revision to be
> extracted.

That's the problem, or better: the reason it works as it does.
Since you have the externals property pinned to a specific revision.
SVN has to honor that. Any changes to the externals must not be
considered ever but only the pinned revision. That's why an update
won't fetch anything new, even if there are commits to the externals.
That's also why the remote status check (in the
check-for-modifications dialog) doesn't show any modifications on the
repository: there were no modifications to the pinned revision (there
can't be).

You might want to consider using an external tool to inform you about
such updates. As it happens, I've written such a tool already:

It does the job and uses as less memory as possible (unlike some other
tools who claim to do the same).


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

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