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

RE: [Bug Report] Branch/tag of a working copy with local modifications does not work properly

From: Gavin Lambert <colnet_at_mirality.co.nz>
Date: Tue, 19 Aug 2014 00:22:35 -0700 (PDT)

> How to recreate the issue
> - Take repository R with two folders:
> - R/trunk
> - R/branches
> - Create the file Text1.txt in trunk and commit.
> - SVN revision: X
> - Modify Text1.txt and commit.
> - SVN revision: X+1
> - Modifiy Text1.txt and execute branch to R/trunk/ver1 selecting "Working copy" in the "Create copy in the repository from:" frame of the branch/tag dialog box
> - SVN revision: X+2
> Now, the log of R/trunk/ver1 shows the following revisions history:
> - X+2
> - X
> while it should show:
> - X+2
> - X+1
> - X

I haven't doubled-checked this, but I suspect it would behave as you expect if you did an SVN Update just after committing rev X+1. I've seen similar behaviour before where a commit sometimes doesn't update something internal. (Most commonly, with two commits in a row the second one will fail because "your working copy is out of date" but only due to the first commit; updating doesn't pull any files but does make SVN happy again.)


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-08-19 09:22:39 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.