On 10/08/11 01:53, Maarten Bezemer wrote:
> Closing the unwanted head with 'hg commit --close-branch' did not
> workaround the problem. The closed branch/head is still imported even
> after trowing away the old bzr import repository and creating a new one
> (with a new import request).
>
> Is this (wrongly importing a closed branch/head) or is due to this
> report and does it get solved automatically when this bug gets fixed
Creating a new import shouldn't really make a difference.
This seems like a bug somewhere. Is it possible to close the default
branch with "hg commit --close-branch" ?
bzr-hg just imports the first revision on the default branch at the
moment, as returned by repo.branchmap(). Can that return closed branches?
Hoi Maarten,
On 10/08/11 01:53, Maarten Bezemer wrote:
> Closing the unwanted head with 'hg commit --close-branch' did not
> workaround the problem. The closed branch/head is still imported even
> after trowing away the old bzr import repository and creating a new one
> (with a new import request).
>
> Is this (wrongly importing a closed branch/head) or is due to this
> report and does it get solved automatically when this bug gets fixed
Creating a new import shouldn't really make a difference.
This seems like a bug somewhere. Is it possible to close the default
branch with "hg commit --close-branch" ?
bzr-hg just imports the first revision on the default branch at the
moment, as returned by repo.branchmap(). Can that return closed branches?
Cheers,
Jelmer