Comment 2 for bug 213946

I use bzr-1.3 && parent branch:
http://bazaar.launchpad.net/%7Ebzr-loom-devs/bzr-loom/1.3/

\\wbr Vitaly

On Wed, Apr 9, 2008 at 2:35 PM, Alexander Belchenko <email address hidden> wrote:
> I can't reproduce this with bzr 1.2, bzr-loom trunk revno.80, and my
> loomified branch with 2 threads. After branching I still have correct
> loom.
>
> Are you sure you record the loom before branching? If yes, can you
> provide small test case how to reproduce this problem?
>
> ** Changed in: bzr-loom
> Status: New => Incomplete
>
>
> --
> After local branch of loom I receive unusable loom
> https://bugs.launchpad.net/bugs/213946
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in A bzr plugin to assist in developing focused patches.: Incomplete
>
>
>
> Bug description:
> bash-3.1# pwd
> /root/projects.bj/soft-meters/dispatcher.loom
> bash-3.1# bzr show-loom
> =>Doxy-Doc
> upstream
> bash-3.1# cd ..
> bash-3.1# bzr branch dispatcher.loom/ dispatcher.loom-2
> Branched 239 revision(s).
> bash-3.1# cd dispatcher.loom-2
> bash-3.1# bzr show-loom
> bash-3.1# bzr nick
> dispatcher.loom-2
> bash-3.1#
>
> I expect to see in dispatcher.loom-2 the branch of dispatcher.loom but not something undefined
>