matthew@seymour:~$ bzr cdiffTo check in code after you have made changes, use the -m flag to add a note,
which is a good idea so that others know what the commit contains:
Click here to view code image
matthew@seymour:~$ bzr commit -m "This fixes bug 204982."
In Bazaar, a commit does not change the remote files but only commits the
change to your local copy. If you want others to see your changes, you must
push the changes to them:
Click here to view code image
matthew@seymour:~$ bzr push sftp://path.to.main/repository
To update the source code in your local repository from the main repository to
make sure you have all the latest changes to the code from other developers,
use the following:
Click here to view code image
matthew@seymour:~$ bzr pull
Many open source projects that use Bazaar host their code using Launchpad,
which is where Ubuntu development takes place. You can find more about it
later in this chapter and also at http://launchpad.net.
Managing Software Projects with Subversion
Subversion was first created in 2000 as a replacement for an older version
control system called the Concurrent Versions System (CVS). At that time,
CVS was 10 years old, and although it served its purpose well, it lacked some
features that developers wanted. Subversion is now actively developed and
widely used.
In Subversion, you check out a file from a repository where code is stored in a
client/server fashion. Then, changes are tracked over any and all files you
check out, including multiple versions of files. You can use Subversion to
backtrack or branch off versions of documents inside the scope of a project. It
can also be used to prevent or resolve conflicting entries or changes made to
source code files by multiple developers. Source code control with
Subversion is done from the command line, as shown in the following
examples. You first need to install Subversion from the Ubuntu software
repositories, where it is called subversion.
You can create a new repository as follows: