Kernel Repository - Revision history

JamesMorris: /* Notes for Subsystem Maintainers */

2017-09-25T05:46:20Z

Notes for Subsystem Maintainers

← Older revision		Revision as of 05:46, 25 September 2017
Line 20:		Line 20:
	== Notes for Subsystem Maintainers ==		== Notes for Subsystem Maintainers ==

	* Code to be merged must be in -~~next~~ for at least two weeks before I can submit to Linus (excepting urgent bugfixes)		* Code to be merged must be in next-testing for at least two weeks before I can submit to Linus (excepting urgent bugfixes)
	* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next		* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to linux-next (like SELinux does)
	* '''Your code must be submitted to my tree by -rc4'''		* '''Your code must be submitted to my tree by -rc4'''
	* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1		* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1
	* Ensure that the branch to be pulled merges cleanly into mine!		* Ensure that the branch to be pulled merges cleanly into mine!

JamesMorris at 05:45, 25 September 2017

2017-09-25T05:45:14Z

← Older revision		Revision as of 05:45, 25 September 2017
Line 3:		Line 3:
	<code>$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git</code>		<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-general''' branch, which is automatically pulled into the linux-next tree. To track this branch:

	<code>$ git checkout --track -b my-next origin/next</code>		<code>$ git checkout --track -b my-next origin/next-general</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.

JamesMorris: /* Notes for Subsystem Maintainers */

2013-11-25T02:09:33Z

Notes for Subsystem Maintainers

← Older revision		Revision as of 02:09, 25 November 2013
Line 22:		Line 22:
	* Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)		* Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)
	* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next		* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next
	'''* Your code must be submitted to my tree by -rc4'''		* '''Your code must be submitted to my tree by -rc4'''
	* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1		* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1
	* Ensure that the branch to be pulled merges cleanly into mine!		* Ensure that the branch to be pulled merges cleanly into mine!

JamesMorris: /* Notes for Subsystem Maintainers */

2013-11-25T02:09:18Z

Notes for Subsystem Maintainers

← Older revision		Revision as of 02:09, 25 November 2013
Line 22:		Line 22:
	* Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)		* Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)
	* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next		* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next
	* ~~I recommend having your~~ code submitted to my ~~try~~ by -rc4		'''* Your code must be submitted to my tree by -rc4'''
	* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1		* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1
	* Ensure that the branch to be pulled merges cleanly into mine!		* Ensure that the branch to be pulled merges cleanly into mine!

JamesMorris: /* Notes for Subsystem Maintainers */

2013-09-20T15:04:45Z

Notes for Subsystem Maintainers

← Older revision		Revision as of 15:04, 20 September 2013
Line 21:		Line 21:

	* Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)		* Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)
	* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next.		* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next
	* I recommend having your code submitted to my try by -rc4.		* I recommend having your code submitted to my try by -rc4
	* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1.		* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1
			* Ensure that the branch to be pulled merges cleanly into mine!

JamesMorris: /* Notes for Subsystem Maintainers */

2013-09-20T15:03:34Z

Notes for Subsystem Maintainers

← Older revision		Revision as of 15:03, 20 September 2013
Line 20:		Line 20:
	== Notes for Subsystem Maintainers ==		== Notes for Subsystem Maintainers ==

	- Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)		* Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)
	- This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next.		* This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next.
	- I recommend having your code submitted to my try by -rc4.		* I recommend having your code submitted to my try by -rc4.
	- Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1.		* Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1.

JamesMorris at 15:03, 20 September 2013

2013-09-20T15:03:14Z

← Older revision		Revision as of 15:03, 20 September 2013
Line 15:		Line 15:

	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.		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.



			== Notes for Subsystem Maintainers ==

			- Code to be merged must be in -next for at least two weeks before I can submit to Linus (excepting urgent bugfixes)
			- This means it must be in my tree (which is pulled to -next) for at least that long, unless you separately push to -next.
			- I recommend having your code submitted to my try by -rc4.
			- Once Linus' merge window opens, no new code can go into -next until -rc1. I can queue your code in a branch in my tree, or you can submit it after -rc1.

JamesMorris at 05:39, 9 April 2012

2012-04-09T05:39:33Z

← Older revision		Revision as of 05:39, 9 April 2012
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.

JamesMorris: 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...

2012-04-09T05:38:29Z

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...

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

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.