loom questions and comments

[Michael Hudson]

Sebastian Kuzminsky wrote:
> John Arbash Meinel wrote:
>> Sebastian Kuzminsky wrote:
>>> Next, on the parent I move down a thread and record again.  When I try
>>> to pull on the child, it says "No revisions to pull", and the state of
>>> the child branch doesnt change.
>>
>> In general, pulling doesn't let you go "back" in history. If you know
>> that is
>> what you want, you can do "bzr pull --overwrite" which ignores the check.
>>
>> Usually 'pull' is meant to update your branch to new work, and going
>> backwards
>> would be a bad thing.
> 
> That works, and your explanation makes sense.
> 
> Is there a better way to get a loom from one branch to another, or to
> access select threads outside their "home" branch?

I generally use 'export-loom' when I want to access individual threads.

I generally have a loom in .../repos/$project/$branch_name (with no
tree) and a lightweight checkout in ..../checkouts/$branch_name and then
bzr export-loom :this puts all the threads in
.../repos/$project/$branch_name/$thread_name.

Cheers,
mwh