Convert bzr

[Adrian Klaver]

On 12/16/2012 01:39 PM, Giorgos Keramidas wrote:
> On Sun, 16 Dec 2012 12:52:54 -0800, Adrian Klaver <adrian.klaver at gmail.com> wrote:
>> On 12/16/2012 12:45 PM, Patrick Mézard wrote:

>>
>> I started with this repo because it was small and simple:) After my
>> last email I decided to run convert against some larger repos and it
>> worked. I was in the process of trying to figure out wht when your
>> email landed. Thanks.
>
> Aha! It seems that hg convert added a tag update commit on the 'default'
> branch, right after it converted everything else to be on the 'aws'
> branch from the original repository — exactly like Patrick said.

So why would that happen? I did not see that happen on other repos I 
converted.


> This should show two disconnected parts in the history graph.  One with
> all your changesets in the 'aws' branch, and one with just the .hgtags
> update that the conversion submitted in the 'default' branch.  Look at
> the two changes you just pasted above: 862c477a9ad0 and 1e9350baa645.
> Their separate branch should be clearly visible ;-)


Yes, I saw that using the method Patrick suggested.

>
> You can fix this for now by cloning the 'aws' branch only of the
> converted repository, and rerunning the conversion script with the
> convert.hg.tagsbranch option, to make sure tag updates happen in the
> 'aws' branch by default:
>
>      hg clone -b aws aws-hg aws-hg-fixed
>      hg convert --config convert.hg.tagsbranch='aws'    \
>          SOURCE-BZR-REPOSITORY                          \
>          aws-hg-fixed
>
> Now the 'aws-hg-fixed' repository should have the tags in the 'aws'
> branch, and only one branch.


Well I figured out how to make a clone up to the revision before the 
tag_update commit. Would it be enough just work off that clone assuming 
I needed no reference back to the original bzr repo? In other words I 
did not need to run convert again.

>
> This should be enough if you are only ever going to have the 'aws'
> branch.  Otherwise, you can keep the tag updates in the 'default'
> branch, and just check out the 'aws' branch for your own work with:
>
>      hg update --clean aws
>
> I hope that helps a bit to understand what happened, and what you do
> now,
>
> Giorgos
>


-- 
Adrian Klaver
adrian.klaver at gmail.com