215
215
we have a checkout, any commits made in the ``~/work/sigil/doodle-fixes/``
216
216
will also show up on ``centralhost``. [#nestedbranches]_ It is also
217
217
possible to have two developers collaborate on one of these branches, just
218
like they would have collaborated on the ``dev`` branch. [#cbranch]_
218
like they would have collaborated on the ``dev`` branch.
220
220
.. [#nestedbranches] It may look odd to have a branch in a subdirectory of
221
221
another branch. This is just fine, and you can think of it as a
222
222
hierarchical namespace where the nested branch is derived from the
225
.. [#cbranch] When using lots of independent branches, having to retype
226
the full URL all the time takes a lot of typing. We are looking into
227
various methods to help with this, such as branch aliases, etc. For
228
now, though, the brztools_ plugin provides the ``brz cbranch`` command.
229
Which is designed to take a base branch, create a new public branch,
230
and create a checkout of that branch, all with much less typing.
231
Configuring ``cbranch`` is outside the scope of this document, but the
232
final commands are similar to:
236
% brz cbranch dev my-feature-branch
238
.. _brztools: http://wiki.bazaar.canonical.com/brzTools
241
226
Merging changes back
242
227
--------------------
282
267
brz+ssh://centralhost/srv/brz/sigil/user-b
284
269
This gives each developer their own branch to work on. And, they can
285
easily create a new feature branch for themselves with just [#cbranch]_
270
easily create a new feature branch for themselves::
288
272
% brz branch brz+ssh://centralhost/srv/brz/sigil/user-a \
289
273
brz+ssh://centralhost/srv/brz/sigil/user-a/feature