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

Re: Update to revision

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: Fri, 30 Mar 2012 14:55:36 +0200

Hi,

On 30 March 2012 13:59, Stefan Küng <tortoisesvn_at_gmail.com> wrote:

> On 30.03.2012 13:56, Tobias Richter wrote:
> > Hi *,
> >
> > if I use the "Update to revision" my local working copy is updated to
> > revision x but all the externals are still coming from the head
> > revision or the explicit revision which was set through the properties.
> >
> > My suggestion: an option that I also get the externals from the revision
> x ...
>
> So you mean if I want to update my TSVN working copy to e.g. revision
> 22700 then all the externals (subversion, apr, neon, ...) it uses should
> also update to that revision?
>
>
I think the OP means that the externals are to be updated to a revision
that was appropriate at the time rev. 22700 was created; he did not mean to
reuse the 22700 as a rev no for the externals.

Now, that info is probably not available for externals that were not linked
to an explicit revision at that time, but for fixed externals it could be
possible. The question remains if this is a feasible option to provide and
if it requires additional SVN support to implement this.

IIRC, there is an option when tagging/branching to freeze externals
pointing to HEAD to a fixed revision? Maybe the OP can use that to achieve
his goal?

-- 
Regards,
Jean-Marc
--
.       ___
.  @@  // \\      "De Chelonian Mobile"
. (_,\/ \_/ \     TortoiseSVN
.   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
.   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2942487
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-03-30 14:55:41 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.