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

Branching in repo browser doesn

From: Stuart MacDonald <scrmacdo_at_sentex.ca>
Date: Fri, 22 Jul 2011 10:46:37 -0700 (PDT)

TortoiseSVN version:

TortoiseSVN 1.6.16, Build 21511 - 64 Bit , 2011/06/01 19:00:35
Subversion 1.6.17,
apr 1.3.12
apr-utils 1.3.12
neon 0.29.6
OpenSSL 1.0.0d 8 Feb 2011
zlib 1.2.5

I searched the users and dev lists, 1.7 change log and issue tracker. Didn't find anything relevant.

What I did:

- open the repo browser
- navigate to <proj>/branches/<branch_1> so <branch_1> is selected
- right-click, select Copy to...
- change just the branch name to <branch_2>, that is, I'm making a new branch from an existing branch
- enter my auth information

What I expected:
- I see the new branch in the repo browser and can further select it, work with it, etc

What actually occurred:
- nothing happened (apparently)

What I further tried:
- F5 to refresh view, no effect
- ctrl-F5 to really refresh view, no effect

It turns out that the new branch was created in the repository, but TortoiseSVN never picked up the change for the repo browser view. I found this out by trying the branch operation again with the same name and having it fail because it already existed.

In further testing I found that, if after the branch operation I then selected <proj>/branches and hit ctrl-F5, then the view refreshed and the new branch was available.

I did expect that the view would update showing the new branch automatically, leaving the <branch_1> selected.

Further, after testing I deleted the test branches. The delete operation works like I expect: the view refreshes to show the absence of the deleted branch without needing further prompting.

I am willing to test fixes.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-07-22 19:53:20 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.