Bazaar For Monotone Users

Both monotone and bazaar are distributed version control systems, but they have some key differences.

Key Things to Know

*What are the essential conceptual and operational differences Bazaar has from Xxx?* (Keep this short but clear enough so that the next section makes sense.)

Core Command Mappings

This section describes some common command mappings from monotone to bazaar.

Getting a checkout

mtn:

 $ mtn clone somemachine.com com.somemachine.branch.name

bzr:

 $ bzr branch http://somemachine.com/this/directory/here

Updating a checkout

mtn:

 $ cd codebase/
 $ mtn pull
 $ mtn update

bzr:

 $ cd codebase/
 $ bzr update

Seeing how a working tree has changed since the last commit

mtn:

 $ mtn status
 [see a list of files that have changed]
 $ mtn pull
 $ mtn log --next 100
 [see a list of the next 100 new revisions in this branch]
 $ mtn diff
 [see a diff of how files have changed]

bzr:

 $ bzr status
 [see a list of files that have changed]
 $ bzr missing
 [see a list of new revisions in the parent branch]
 $ bzr diff
 [see a diff of how files have changed]

In both of these cases, you'll get a diff that you can review prior to commit.

Comitting code in a checkout

mtn:

 $ mtn commit -m'some description of whats being committed.'

bzr:

 $ bzr commit -m'some description of whats being committed.'

In both of these cases, the new changes will be saved to either the local database (Monotone) or branch (Bazaar).

Other Command Mappings

(Same as the previous section but covering the non-core commands.)

Other Things To Know

Other interesting things about Bazaar for users of Xxx to know. References to Where Bazaar Is Better, Where Bazaar Is Weaker and how to migrate repositories are appropriate here.