On 6/12/2016 02:07, Olivier Sannier wrote:
> Thanks for the reminder, I thus believe that if I use @HEAD on my
> externals, this won't solve the issue.
> However, wouldn't it be possible to have a special command in
> TortoiseSVN that does this? I mean, here are the steps it would do
> internally:
>
> Update each external to the requested revision
> Update the main working copy to the requested revision, ignoring externals.
>
> I would be nice to have this available instead of having to do it manually.
When you create a branch, you are shown some UI that lets you lock the
externals to their current revision (at the time of branch creation)
rather than continuing to follow HEAD. This is especially useful when
creating release branches.
When you later switch to that branch, they will be updated according to
what had been chosen at the time the branch was created. (And, of
course, any updates made by later commits on the branch, if any.)
In general, "update to revision" should not be something that you're
doing on a regular basis -- it's intended for rare cases when trying to
track down the history of a bug or otherwise make a historic build other
than an active release branch or tag. For things that you are switching
between frequently, use branches.
Also in general it doesn't make sense for "update to revision" to change
where externals are pointing because they're mainly intended to be
pointing at external repositories (hence the name) which have completely
unrelated revision numbers.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3196360
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-12-08 00:51:56 CET