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

Re: [TSVN] Re: Flyspray task #141 - Project property to disable scanning of externals

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2005-07-28 11:05:59 CEST

SteveKing wrote:
> On 7/27/05, Simon Large <simon@skirridsystems.co.uk> wrote:
>
>>issues@tortoisesvn.tigris.org wrote:
>>
>>>Task summary: Project property to disable scanning of externals
>>
>>You could always move the externals into a path parallel to trunk
>>instead of below trunk ;-) Then you wouldn't need to scan them on
>>commit, or get slowed down for a normal (day-to-day) update of trunk.
>
>
> But if you do that, it wouldn't be much better than to just put
> something like "check out project A from URL, project B from URL, ....
> and put them in the dir X".

It's not that bad. Checkout TSVN trunk from URL, checkout externals from
URL. That's only 2 checkouts.

> If you include the externals inside your project, you just have to
> check out *one* URL and you're done - isn't that the whole point of
> externals?

Mostly, yes. But in this case all the externals point to tags, not live
development branches, so they only need updating when the svn:externals
value changes to a different tag. Don't you get bored when you run
update on trunk, checking for updates to subversion which you know
aren't there?

I would expect the nightly build to update every time because it's done
by a cron job which doesn't care about waiting an extra minute.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jul 28 11:05:54 2005

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.