RE: Re: [1.7.1] Unexpected: Tagging working copy with externals modify the tag.

Dear Stefan,

I've experienced a similar issue as Laurent did, and am currently using tagging/branching from the working copy (selected via the commit dialogue's radio button). However, this IMHO is rather a workaround.

We've been using a pre-commit script in order to check if each external has a fixed peg revision assigned. This really prevented a lot of hassle in the past!

Now the new ToirtoiseSVN client brought that great feature of automatically fixing the revision numbers without the need to cumbersome manually editing, but unfortunately using multiple checkins.

Our pre-commit script now will fail due to the revision assignments missing. However, an explicit checkin from the working copy bears the risk of modifications only propagating to the particular tag, beeing missed in the trunk.

In my opinion it might be the best way to *always* locally fix the externals' revisions, apply the tag/branch and restore the revision to their original state afterwards. What do you think?

Kind regards
Markus

> On 26.10.2011 11:41, Laurent Leroy wrote:
> > I let the default value for revision while tagging, so the version is
> > explicit revision and is the default working copy revision. (which is
> > actually the head revision in repository) Is that the problem ?
>
> Yes, that option too creates the tag/branch directly in the repository.
>
> Stefan
>
> --
> ___
> 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=2883293

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-21 15:41:51 CET