GitTheSource

Differences between revisions 7 and 16 (spanning 9 versions)
Revision 7 as of 2010-06-21 09:01:48
Size: 2251
Editor: 85-210-146-14
Comment:
Revision 16 as of 2024-01-23 08:28:28
Size: 4155
Editor: anthonywong
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
All of the Ubuntu Kernel source is maintained under {{{git}}}. The source for each release is maintained in its own git repository on {{{kernel.ubuntu.com}}}. These can be browsed in [[http://kernel.ubuntu.com/git|gitweb]], the official Ubuntu trees are in the {{{ubuntu/}}} directory. The Ubuntu Linux kernel git repository is located at git://kernel.ubuntu.com/ubuntu/ubuntu-<release>.git or http://kernel.ubuntu.com/git-repos/ubuntu-<release>.git. To obtain a local copy you can simply git clone the repository for the release you are interested in as below. The {{{git}}} command is part of the {{{git-core}}} package: The source for each release is maintained in its own git repository on Launchpad.

The git repository is listed in the `Vcs-Git:` header in the source package and is of the following form:
Line 6: Line 8:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-<release>.git git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/<source package>/+git/<series>}}}

For example, the standard Jammy kernel is available at:

    {{{
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy}}}

There is a tree for each of the currently supported releases as well as any open development and upcoming releases. For example:

 || focal || git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal ||
 || jammy || git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy ||
 || noble || git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble ||

Replace your intended Ubuntu series in the above URL, and pull the source for the kernels you need.

The distro kernel is always on the `master` branch in these repositories. Each release also has a `master-next` branch containing the commits that will go into the `master` branch and become the next SRU release for that series.

A number of releases also have other source packages which represent other related but divergent kernels for other purposes. For example, there is a specialized AWS kernel available in the linux-aws source package. (Previously these sorts of things were done in [[KernelTeam/TopicBranches|Topic Branches]] and some older kernels and projects still use them.)

If you cannot use the git protocol (perhaps because of a firewall), you can use the slower https protocol. For example:

 || jammy || https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy ||
 || noble || https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble ||

=== Obtaining a copy ===

To obtain a local copy you can simply `git clone` the repository for the release you are interested in. The {{{git}}} command is part of the {{{git}}} package.

For example to obtain the Jammy tree:

    {{{
git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy}}}

This will download several hundred megabytes of data. If you plan on working on more than one kernel release you can save space and time by downloading the upstream kernel tree, and use it as a reference. Note that once these two trees are tied together you cannot simply delete or move the virgin Linus tree without manually updating `.git/objects/info/alternates` in your Ubuntu kernel tree:

    {{{
git clone git://kernel.ubuntu.com/ubuntu/linux.git
git clone --reference linux git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
git clone --reference linux git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble
Line 9: Line 49:
For example to obtain the maverick tree: In each case you will end up with a new directory {{{<ubuntu-release>}}} containing the source and the full history which can be manipulated using the {{{git}}} command from within each directory.

If you are an advanced git user, you can also add each Ubuntu series as a remote so that you can have all kernel series you need in a single directory. For example,
Line 12: Line 54:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git git remote add jammy git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
git fetch jammy
git checkout -b jammy --track jammy/master
git checkout -b jammy-next --track jammy/master-next
Line 15: Line 60:
This will download several hundred megabytes of data. If you plan on working on more than one kernel release you can save space and time by downloading the upstream kernel tree. Note that once these two trees are tied together you cannot remove the virgin Linus tree without damage to the Ubuntu tree:

    {{{
git clone git://kernel.ubuntu.com/ubuntu/linux-2.6
git clone --reference linux-2.6 git://kernel.ubuntu.com/ubuntu/ubuntu-karmic.git
git clone --reference linux-2.6 git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git
}}}

In each case you will end up with a new directory {{{ubuntu-<release>}}} containing the source and the full history which can be manipulated using the {{{git}}} command from within each directory.

By default you will have the latest version of the kernel tree, the master tree. You can switch to any previously released kernel version using the release tags. To obtain a full list of the tagged versions in the release as below:
By default you will have the latest version of the kernel tree, the master tree. You can switch to any previously released kernel version using the release tags. To obtain a full list of the tagged versions in the release, use the `git tag` command below:
Line 29: Line 64:
Ubuntu-2.6.27-7.10
Ubuntu-2.6.27-7.1
1
Ubuntu-2.6.27-7.12
Ubuntu-2.6.27-7.13
Ubuntu-2.6.27-7.14
$
}}}
Ubuntu-5.4.0-47.51
Ubuntu-5.4.0-48.52
Ubuntu-5.4.0-49.53
Ubuntu-5.4.0-51.56
Ubuntu-5.4.0-5
2.57
...}}}
Line 36: Line 71:
To look at the {{{2.6.27-7.13}}} version you can simply checkout a new branch pointing to that version: To look at the {{{Ubuntu-5.4.0-52.57}}} version you can simply checkout a new branch pointing to that version:
Line 39: Line 74:
git checkout -b temp Ubuntu-2.6.27-7.13 git checkout -b temp Ubuntu-5.4.0-52.57
Line 42: Line 77:
You may then manipulate the release for example adding new commits. You may then manipulate the release - for example, by adding new commits.

Obtaining the kernel sources for an Ubuntu release using git

The source for each release is maintained in its own git repository on Launchpad.

The git repository is listed in the Vcs-Git: header in the source package and is of the following form:

  • git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/<source package>/+git/<series>

For example, the standard Jammy kernel is available at:

  • git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy

There is a tree for each of the currently supported releases as well as any open development and upcoming releases. For example:

  • focal

    git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal

    jammy

    git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy

    noble

    git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble

Replace your intended Ubuntu series in the above URL, and pull the source for the kernels you need.

The distro kernel is always on the master branch in these repositories. Each release also has a master-next branch containing the commits that will go into the master branch and become the next SRU release for that series.

A number of releases also have other source packages which represent other related but divergent kernels for other purposes. For example, there is a specialized AWS kernel available in the linux-aws source package. (Previously these sorts of things were done in Topic Branches and some older kernels and projects still use them.)

If you cannot use the git protocol (perhaps because of a firewall), you can use the slower https protocol. For example:

Obtaining a copy

To obtain a local copy you can simply git clone the repository for the release you are interested in. The git command is part of the git package.

For example to obtain the Jammy tree:

  • git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy

This will download several hundred megabytes of data. If you plan on working on more than one kernel release you can save space and time by downloading the upstream kernel tree, and use it as a reference. Note that once these two trees are tied together you cannot simply delete or move the virgin Linus tree without manually updating .git/objects/info/alternates in your Ubuntu kernel tree:

  • git clone git://kernel.ubuntu.com/ubuntu/linux.git
    git clone --reference linux git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
    git clone --reference linux git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble

In each case you will end up with a new directory <ubuntu-release> containing the source and the full history which can be manipulated using the git command from within each directory.

If you are an advanced git user, you can also add each Ubuntu series as a remote so that you can have all kernel series you need in a single directory. For example,

  • git remote add jammy git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
    git fetch jammy
    git checkout -b jammy --track jammy/master
    git checkout -b jammy-next --track jammy/master-next

By default you will have the latest version of the kernel tree, the master tree. You can switch to any previously released kernel version using the release tags. To obtain a full list of the tagged versions in the release, use the git tag command below:

  • $ git tag -l Ubuntu-*
    Ubuntu-5.4.0-47.51
    Ubuntu-5.4.0-48.52
    Ubuntu-5.4.0-49.53
    Ubuntu-5.4.0-51.56
    Ubuntu-5.4.0-52.57
    ...

To look at the Ubuntu-5.4.0-52.57 version you can simply checkout a new branch pointing to that version:

  • git checkout -b temp Ubuntu-5.4.0-52.57

You may then manipulate the release - for example, by adding new commits.

Kernel/Action/GitTheSource (last edited 2024-01-23 08:28:28 by anthonywong)