lp:~spiv/bzr-loom/plugin-init

Branch merges

Propose for merging

No branches dependent on this one.

On hold for merging into lp:bzr-loom

Loom Developers: Pending requested 2010-08-13

Diff: 836 lines (+244/-220)

2 files modified

branch.py (+89/-210)
formats.py (+155/-10)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #617212: "bzr selftest -s bt.per_interbranch Loom" finds 0 tests

Medium

Triaged

Link a bug report

Related blueprints

127. By Andrew Bennetts on 2010-08-13

Follow bzrlib conventions for imports, use lazy_imports in branch.py, and register InterLoomBranch in formats.py so that it is always registered for the bzr per_interbranch test suite.

126. By Vincent Ladeuil on 2010-07-16

(vila) When threads exist ``bzr nick`` should still change the branch nick

125. By Robert Collins on 2010-07-03

Fixup tests.

124. By Robert Collins on 2010-07-02

Make create-thread a little clearer in its help.

123. By Robert Collins on 2010-07-02

``bzr loomify`` explicitly checks that branches being converted are not Looms
already. This should not have been needed, but apparently it was.
(Robert Collins, #600452)

122. By Robert Collins on 2010-07-02

``bzr nick`` will now rename a thread rather than setting the current thread
pointer to an invalid value. (Robert Collins, #203203, #260947, #304608)

121. By Robert Collins on 2010-07-02

Change from using nick=thread to _set_nick(thread) in loom internals and tests.

120. By Robert Collins on 2010-07-01

A new revision specifier ``below:`` has been added. (Robert Collins, #195282)

The ``thread:`` revision specifier will no longer throw an attribute error
when used on a normal branch. (Robert Collins, #231283)

119. By Robert Collins on 2010-06-30

Move version details to a separate file to remove duplication.

118. By Robert Collins on 2010-06-29

``bzr combine-thread`` will no longer combine threads without ``--force``
when the thread being removed has work not merged into either the thread
above or below. (Robert Collins, #506235)