Difference between revisions of "Kernel Repository"
JamesMorris (talk | contribs) (New page: To develop patches for the kernel security subsystem, use git to clone the linux-security tree: $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git Unles...) |
JamesMorris (talk | contribs) |
||
| Line 1: | Line 1: | ||
To develop patches for the kernel security subsystem, use git to clone the linux-security tree: | To develop patches for the kernel security subsystem, use git to clone the linux-security tree: | ||
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git | <code>$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git</code> | ||
Unless otherwise requested, all development should be done against the next branch, which is automatically pulled into the linux-next tree. To track this branch: | Unless otherwise requested, all development should be done against the next branch, which is automatically pulled into the linux-next tree. To track this branch: | ||
$ git checkout --track -b my-next origin/next | <code>$ git checkout --track -b my-next origin/next</code> | ||
You can also fetch this branch into an existing local kernel repository and manage it via git remote. Refer to the git documentation and the Kernel Hackers' Guide to git for more information. | You can also fetch this branch into an existing local kernel repository and manage it via git remote. Refer to the git documentation and the Kernel Hackers' Guide to git for more information. | ||
Revision as of 05:39, 9 April 2012
To develop patches for the kernel security subsystem, use git to clone the linux-security tree:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
Unless otherwise requested, all development should be done against the next branch, which is automatically pulled into the linux-next tree. To track this branch:
$ git checkout --track -b my-next origin/next
You can also fetch this branch into an existing local kernel repository and manage it via git remote. Refer to the git documentation and the Kernel Hackers' Guide to git for more information.
Patches for review and submission should be generated with git format-patch. If you want a git branch pulled directly, use git request-pull.
A web-browsable interface via gitweb may be found at: http://git.kernel.org/?p=linux/kernel/git/jmorris/linux-security.git;a=summary
Patches should be sent as inline text to linux-kernel @ vger.kernel.org, and preferably cc'd to linux-security-module @ vger.kernel.org and jmorris @ namei.org.