[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tortoisesvn-users
Subject:    Re: Update to revision
From:       Simon Large <simon.tortoisesvn () gmail ! com>
Date:       2012-03-30 13:01:05
Message-ID: CADfBBgPCSW9oGOQvb3wddcYxOj9MS4SsW3R+qgfU0Aggo2OAhQ () mail ! gmail ! com
[Download RAW message or body]

On 30 March 2012 13:55, Jean-Marc van Leerdam <j.m.van.leerdam@gmail.com> wrote:
> Hi,
>
> On 30 March 2012 13:59, Stefan Küng <tortoisesvn@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?

That is exactly what you have to do when branching/tagging, and when
using an external repository. And that is what our docs recommend.
However there is another use case where you are using externals as a
convenience to reference some other part of your own repository, for
example a common library. In that case for trunk development you would
normally be working with the HEAD revision for both project and
externals. If you then want to go back in time perhaps to track down
when a bug was introduced, you would want both project and externals
to go back to the same earlier revision.

So maybe what the OP wants is an option to update any externals which
are in the same repository to be at the specified revision.

Simon

-- 
:          ___
:   oo   // \\         "De Chelonian Mobile"
: (_,\/ \_/ \       TortoiseSVN
:    \ \_/_\_/>      The coolest Interface to (Sub)Version Control
:    /_/    \_\       http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2942491

To unsubscribe from this discussion, e-mail: [users-unsubscribe@tortoisesvn.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]