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

Re: Handling file level externals

From: Kevin Radke <kmradke_at_gmail.com>
Date: Wed, 24 Sep 2008 14:16:11 -0500

On Wed, Sep 24, 2008 at 2:06 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> Kevin Radke wrote:
>> On Wed, Sep 24, 2008 at 12:08 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>>> Kevin Radke wrote:
>>>> Has anyone given thought on how TortoiseSVN should handle the future
>>>> 1.6 file level
>>>> externals capabilities?
>>>>
>>>> http://subversion.tigris.org/svn_1.6_releasenotes.html#file-externals
>>>>
>>>> The code just hit trunk, so I'm not complaining it isn't used yet, just curious
>>>> if anything would need to be upgraded in TortoiseSVN, other than using
>>>> trunk versions of the SVN api?
>>>>
>>>> I've been wanting to get a Tortoise build environment setup anyway, and
>>>> if it just requires a rebuild this may be a good enough reason to do it now.
>>> You can try a nightly build from trunk. The trunk uses currently r33254
>>> of the svn trunk.
>>
>> A minor change made it into r33265 today. Do you always build the nightly
>> with latest, or do you just periodically sync with svn trunk?
>
> I usually update once or twice a week to the HEAD of the svn trunk. I
> can't have the externals point to HEAD directly since that would cause a
> lot of build breaks. After all, it's the trunk where the API's change a lot.

Yeah, I figured you wouldn't be using HEAD. I now see the update.txt
file for the nightly build contains the svn external revision number.

Thanks!
Kevin R.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-09-24 21:16:22 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.