Last year I wrote a blog post about how to migrate away from Bazaar, a distributed version control system, originally developed by Canonical, to git.
While I still think this is the only way forward, here, at Canonical, working in the Launchpad team, we still have a couple of Bazaar repositories around, which cannot be easily migrated, as they are both integrated into deployment processes, and used by other teams.
basic commands to get around
Please note: Breezy (brz) is a friendly fork of the Bazaar (bzr) project. Nowadays, it is strongly recommended to use Breezy.
While Bazaar and git are different, the basic commands are pretty similar. So if you know git, you will probably recognize the following commands:
clone a repository
brz branch lp:brz
update a local repository
brz pull
create a local branch
brz branch lp:brz <name-of-branch>
Please note: You should do this outside the cloned repository, as this will create a new folder.
add changes
brz add <filename>
commit changes
brz commit
or
brz commit -m "message"
push changes
brz push lp:~<my-account>/brz/<name-of-branch>
create a merge proposal
-> go to the branch in your account
( https://code.launchpad.net/~<my-account>/brz/<name-of-branch> )
and click on “Propose for merging”
show log
brz log
Please note: As there is no builtin pager, you probably want to use
brz log | less
show a single rev
show revision number 3
brz log -c3
… including code changes
brz log -c3 -p