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

Re: [Subclipse-users] Switching the branch of a subfolder does not take effect until the parent folder is manually updated.

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-03-10 01:49:47 CET

On 3/9/07, John Shields <jshields@mechanicnet.com> wrote:
>
> I have found that when I switch the branch of a subfolder that the UI
> does not register the switch nor, more importantly, do commits go into
> the switched branch until I've updated the parent folder manually. What
> is interesting and troubling, though, is that the properties of the
> folder and of any files in the folder do reflect the switch. But again,
> commits don't seem to go to the switched branch.
>
> To reproduce:
>
> 1. Select a subfolder of a project and switch it to another branch.
> 2. Make a change to a file in that subfolder.
> 3. Commit the file.
> 4. Check the SVN repository directly to see where the commit "landed".
>
> In my tests, the change always goes to the original branch before the
> switch. However, if I follow these steps it works as expected:
>
> 1. Select a subfolder of a project and switch it to another branch.
> 2. Manually perform an "update" operation on the parent folder. (This
> causes the icon on the subfolder to reflect it's "switched" status.)
> 3. Make a change to a file in that subfolder.
> 4. Commit the file.
> 5. Check the SVN repository directly to see where the commit "landed".

I do not think this is possible and here is why. When we do a commit, we
are just running a Subversion API. We do not tell the commit where to go.
Subversion code is handling everything based on the info in its working
copy. Likewise, when we run switch, we just call a Subversion API and it
does all the work. I do not think it is possible Subversion has any
problems in this area.

Do you have your repository setup to send commit emails? That is always a
good way to see what happened. Try running svn log on the root of the
repository and look at what it says it did on some of these commits.

Now that being said, I would not be surprised if we had some UI bug where we
led you to believe this is what happened. If you can narrow that down let
me know more info. It just is not possible that commit could go to the
wrong place. We could not make Subversion do that if we wanted to, just as
you could not by using the command line client.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on Sat Mar 10 01:59:51 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.