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

Re: Fwd: svn1.5 seems to fail simple merge-tracking scenario

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 20 Feb 2009 16:05:19 -0500

On Fri, Feb 20, 2009 at 3:48 PM, Brian Erickson
<erickson_at_bauercontrols.com> wrote:
> Good lord this is complicated. Subversion doesn't seem to be doing a
> good job making my life easier. I always knew exactly what to do when
> we used PVCS. Now, I find myself deleting the .svn folders and copying
> files way more than makes me comfortable.
> It seems that's what I have to do to clean up my mess.
> This morning I reintegrated from a branch (./branches/TRHistoryWnd) back
> into the trunk (./trunk/pcs). Since, then at least 2 of us have
> committed changes into the branch.
> It seems like what I need to do is:
> 1) Checkout the TRHistoryWnd branch and delete all the .svn folders.
> 2) Delete the TRHistoryWnd branch
> 3) Create a branch call TRHistoryWnd
> 4) Checkout the new TRHistoryWnd branch
> 5) Copy the tree made in step on over top of my new working copy
> 6) Commit back to my branch.
> 7) Don't ever re-integrate until you're completely done.
> Thanks for your attempts at helping me.

There is no question that you do NOT have to do what you are doing,
and I doubt anyone here would have suggested that.

You do not say what you want to do, but if you want to get those two
revisions from the branch to trunk, the simplest way is to just name

Let's assume the two revisions committed were 100 and 105.

From a trunk WC:

$ svn merge -c100,105 ^/branch/TRHistoryWnd
$ svn ci -m "Merge r100 and 105 from TRHistoryWnd"

Then delete and optionally recreate the branch.

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-20 22:06:34 CET

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

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