Bzr

Differences between revisions 1 and 2
Revision 1 as of 2013-03-19 14:43:52
Size: 1437
Editor: zequence
Comment:
Revision 2 as of 2013-03-19 14:48:15
Size: 1538
Editor: zequence
Comment:
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
 /!\ Do not add several features committing them all at once. This makes it hard to oversee changes. A feature change may mean that you edit more than one file though. /!\ '''Do not add several features and then commit them all at once. This makes it hard to oversee changes. However, making a feature change often means that you edit more than one file. So, it is the feature that should be commited, not each changed file by itself.'''

What is Bazaar?

Bazaar is a GNU version control system, sponsored by Canonical used for keeping track of sources at code.launchpad.net. Most, or all Ubuntu sources exist as bzr branches.

bzr command cheat sheet

Get Ubuntu Source

Getthe source for a development release branch:

bzr branch ubuntu:<package>

For example:

bzr branch ubuntu:jackd2

Or, if you want the source for a specific release:

bzr branch ubuntu:<release>/<package>

For example:

bzr branch ubuntu:precise/jackd2

bzr commits

Warning /!\ Do not add several features and then commit them all at once. This makes it hard to oversee changes. However, making a feature change often means that you edit more than one file. So, it is the feature that should be commited, not each changed file by itself.

To make a commit, you would first make changes. To make new files commitable, you would first need to:

bzr add <yournewfile>

While you'll probably seldom do it this way (if you're working on a debian package), this is how to create a standard bzr commit:

bzr commit -m "a description of your commit"

If you're working on a Debian package, you'll first edit debian/changelog, and then use debcommit. debcommit reads debian/changelog and uses the descriptions of changes from there.

debcommit

UbuntuStudio/Bzr (last edited 2013-05-17 01:32:45 by zequence)