status should indicate that a loom needs recording

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?

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
>

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?
i'm not sure.

>
> ** 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
>

vitaly.v.ch пишет:
> I use bzr-1.3 && parent branch:
> http://bazaar.launchpad.net/%7Ebzr-loom-devs/bzr-loom/1.3/

I have no problems even with bzr 1.3.

Vitaly, have you done 'bzr record' in your loom?

How at now I can see there was done 'bzr record' in my loom?

bzr st don't show anything about it

\\wbr Vitaly Chernookiy.

On Thu, Apr 10, 2008 at 12:35 AM, Robert Collins
<email address hidden> wrote:
> Vitaly, have you done 'bzr record' in your loom?
>
>
> --
> 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
>

On Thu, 2008-04-10 at 05:47 +0000, vitaly.v.ch wrote:
> How at now I can see there was done 'bzr record' in my loom?
>
> bzr st don't show anything about it

You're right, st should definitely show you something; but it doesn't
yet.
-Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

I have tested local branches manually and they definitely still work.

there was branch of unrecorded loom.

\\wbr Vitaly Chernookiy

On Mon, Aug 4, 2008 at 6:21 AM, Robert Collins
<email address hidden> wrote:
> I have tested local branches manually and they definitely still work.
>
> --
> 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 Bazaar Loom: 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
>

On Mon, 2008-08-04 at 07:37 +0000, vitaly.v.ch wrote:
> there was branch of unrecorded loom.

Thanks - definitely need to fix the UI then.

 summary status should indicate that a loom needs recording
 status triaged
 importance medium
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

On Mon, 2008-08-04 at 07:37 +0000, vitaly.v.ch wrote:
> there was branch of unrecorded loom.

Thanks - definitely need to fix the UI then.

 summary "status should indicate that a loom needs recording"
 status triaged
 importance medium
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

As I understand branch must branching last recorded loom and warn
about unrecorded changes

\\wbr Vitaly Chernookiy

On Mon, Aug 4, 2008 at 7:55 AM, Robert Collins
<email address hidden> wrote:
> On Mon, 2008-08-04 at 07:37 +0000, vitaly.v.ch wrote:
>> there was branch of unrecorded loom.
>
> Thanks - definitely need to fix the UI then.
>
> summary "status should indicate that a loom needs recording"
> status triaged
> importance medium
> --
> GPG key available at: <http://www.robertcollins.net/keys.txt>.
>
>
> ** Summary changed:
>
> - After local branch of loom I receive unusable loom
> + status should indicate that a loom needs recording
>
> --
> status should indicate that a loom needs recording
> https://bugs.launchpad.net/bugs/213946
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Loom: Triaged
>
> 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
>

On Mon, 2008-08-04 at 07:49 +0000, Robert Collins wrote:
> On Mon, 2008-08-04 at 07:37 +0000, vitaly.v.ch wrote:
> > there was branch of unrecorded loom.
>
> Thanks - definitely need to fix the UI then.

Hi Rob,

I've been wondering why it doesn't just record on every commit,
or rather after every branch tip change, is this not appropriate?

Thanks,

James

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Vitaly

Vitaly Chernooky
Senior Software Engineer at GlobalLogic
Ukraine

Confirm that you know Vitaly Chernooky:
https://www.linkedin.com/e/orajw9-h71n7pfp-1x/isd/8629426284/vYPvSF8j/?hs=false&tok=1PcmYiOhiHIlo1

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/orajw9-h71n7pfp-1x/7aAiatFvhnufrp44UevP7Kzv3CCNc8f-aX8Vhhq/goo/213946%40bugs%2Elaunchpad%2Enet/20061/I2902414428_1/?hs=false&tok=3HJ7-ssPSHIlo1

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.