Differences between revisions 16 and 17
Revision 16 as of 2007-05-09 21:43:30
Size: 3569
Editor: 82-71-20-114
Comment: Amended "around 110Megs of data" to reflect the present size of the tree.
Revision 17 as of 2007-05-14 10:50:52
Size: 3884
Editor: chello080108233167
Comment: added comment on git:-urls
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:

''Comment from GregorRosenauer'': The rsync://-URIs are not mentioned anymore on the official [ git]-pages, but there are git://-URIs which work perfectly (also on update using "pull"), e.g., for gutsy:
 * git://


Git is the new SCM used by the Linux kernel developers. Ubuntu has adopted this tool for our own Linux kernel source code so that we can interact better with the community and the other kernel developers.

Current GIT Trees

  • gutsy: rsync://
  • feisty: rsync://
  • edgy: rsync://
  • dapper: rsync://

(actually there are a few more and of special note are the -updates git trees (nb: there can be more than one -updates tree per stable release). To find out what else is available try browsing and searching for ubuntu)

Comment from GregorRosenauer: The rsync://-URIs are not mentioned anymore on the official [ git]-pages, but there are git://-URIs which work perfectly (also on update using "pull"), e.g., for gutsy:

  • git://

Getting GIT

To obtain the git binaries, simply install the git-core package from dapper, e.g.:

sudo apt-get install git-core

Note that the git package is an entirely different tool which will not do what you want.

Getting the Ubuntu Linux kernel repo

The Ubuntu Linux kernel git repository is located at rsync:// To download a local copy of the repo, use this command:

  git clone rsync:// ubuntu-gutsy

This will take some time depending on your connection. There's around 220 MiB of data to download currently (and this always increases).

Once this is complete, you can keep your tree up-to-date by running this command:

  git pull

Pushing changes to the main repo

Since the main repo is not publicly writable, the primary means for sending patches to the kernel team is using git-format-patch. The output from this command can then be sent to the [ kernel-team] mailing list.

Alternatively, if you have a publicly available git repository for which changes can be pulled from, you can use git-request-pull to generate an email message to send to the [ kernel-team] mailing list.

Commit templates

In debian/commit-templates/ there are several templates that must be used when commiting changes that you expect to be integrated with the Ubuntu kernel repo. The commit templates contain comments for how to fill out the required information. Also note that all commits must have a Signed-off-by line (the "-s" option to git-commit). A typical git-commit command will look like:

  git-commit -s -F debian/commit-templates/patch -e

Note that the -e (edit) option must follow the -F option, else git will not let you edit the commit-template before committing.

An example commit log will look like such:

  UBUNTU: scsi: My cool change to the scsi subsystem

  UpstreamStatus: Merged with 2.6.15-rc3

  My cool change to the scsi subsystem makes scsi transfers increase
  magically to 124GiB/sec.

  Signed-off-by: Joe Cool Hacker <>

Ubuntu kernel developers (with access to rookery)

The kernel team has a private git repo located on rookery in /srv/kernel-team. Take care when pushing to this repository.

You can, if you want, create a clone for yourself in this directory, and just have your changes pulled when ready.

More information

Please read the documentation included with the git source for more details on git commands.


KernelTeam/KernelGitGuide (last edited 2010-06-28 23:55:41 by c-76-105-148-120)