Convert bzr

[Adrian Klaver]

On 12/16/2012 12:45 PM, Patrick Mézard wrote:

>
>>
>>
>> This might be a good time to ask what is supposed to happen?
>> I am working under the assumption that using convert creates a new directory with a .hg subdirectory and the working files from the original repo(this case bzr) copied over. Is this what is intended or am I making a false assumption?
>
> It creates a new repository but does not checkout anything. Here you may have an issue with a simple "hg update" because convert created a misplaced tag changeset (meaning you have two heads on default branch). Running:
>
>    $ hg branches

Yes, this seems to be the problem.

aklaver at panda:~/aws-hg> hg branches
default                       33:1e9350baa645
aws                           32:862c477a9ad0


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.

>
> should display converted branches. If the one you want is "default", run:
>
>    $ hg heads default
>
> this may display more than one changeset, including the tags one. Pick the one you want (not the tags one) and use it with "hg update".
>
> Otherwise, "hg update -C BRANCH" should give you the branch you want.
>
> Running a graph viewer on the repository may also help clarifying things.

New to hg, so how do I do that?


> --
> Patrick Mézard
>


-- 
Adrian Klaver
adrian.klaver at gmail.com