subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Johnson <e...@tibco.com>
Subject Re: Reoganizing svn structure and error "shares no common ancestry"
Date Tue, 17 Mar 2015 22:14:19 GMT
Does switching to a new branch work before the reorganization that you did?

What version of Subversion are you using?

Can you reproduce the problem with a mock version of your repository?

When you do an svn log of your new branch, does the history go back to a
common revision with the new trunk? Likewise, with your new trunk, does an
svn log show a common revision with the branch?

Eric


On Mon, Mar 16, 2015 at 3:18 AM, Buddy Butterfly <buddy.butterfly@web.de>
wrote:

>
> Hi,
>
> finally we would like to restructure our badly structured svn repo.
> Over time a lot of stuff flew into this repo. I have used kdesvn for
> moving the trees online in the repo. kdesvn does a copy and delete
> when moving. I have also tried to use a svn move. Steps were as follows:
>
> 1. Created a new repo path to the project.
> 2. Created branches, tags and trunk below ist.
> 3. Moved (like described above) original project below the new trunk.
> 4. Similar like 3. for branches with creating the branches/<branch> and
>    moving the old branches to the new ones.
> 5. Checked out the new trunk.
> 6. Tried to switch to one of the new branches.
>
> Step 6. always give the error switching not possible "shares no common
> ancestry".
>
> The moving like described above is very convenient and would allow the
> reorg
> in an acceptable time frame. How is it possible to do this and create or
> manipulate the history such that a common ancester will be created?
>
> Do you propose another workflow to acomplish this in an easy way?
>
> Thanks a lot and cheers,
> Buddy
>

Mime
View raw message