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

Re: Making a branch the new trunk

From: Peter Werner <l.svn_at_vasas.no-ip.org>
Date: 2006-06-13 15:35:13 CEST

> I'd like to disagree, here. You may not actually want the vast, detailed
> history of the branch integrated into the trunk, especially the history of
> failed changes.

Interesting point. I agree that there can be such branches where you
experiment, fool around and then merge to trunk. Here it's an advantage
that you don't have the history.

My guess is that the original question is another usecase where one
branch slowly became the head branch. It's role is trunk so just the
name has to be changed.

I have a similar use case, and for me the most important is to keep the
complete history. (If something braks I want to check where it

A sidenote, you may want to keep the original trunk as a tag:
svn mv <URL BASE>/trunk <URL BASE>/tags/abandoned-trunk
svn mv <URL BASE>/branches/my-loved-branch <URL BASE>/trunk

I don't know any better way than doing it in two commits.

> ... famous "Cannot replace directory from within" message ...
I tested it and I did not get any messages. Most probably it is the
result to have some non-versioned files in the directory that prevented
removing it.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 13 15:37:35 2006

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.