|Line 1:||Line 1:|
To develop patches for the kernel security subsystem, use [http://git-scm.com/ git] to clone the
To develop patches for the kernel security subsystem, use [http://git-scm.com/ git] to clone the [http://git.kernel.org/?p=linux/kernel/git/jmorris/security-testing-2.6.git;a=summary security-testing-2.6 tree]:
Latest revision as of 09:35, 7 January 2009
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6
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.
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.