Submit patches to Openembedded - Revision history

Koan: /* Submit patches to Openembedded (core) */

2024-06-27T09:06:09Z

Submit patches to Openembedded (core)

← Older revision		Revision as of 09:06, 27 June 2024
Line 1:		Line 1:
	== Submit patches to Openembedded (core) ==		== Submit patches to Openembedded (core) ==
	~~Submitting patches~~ to ~~oe-core is slightly different than what was used with oe-classic~~.		Contributions to the Yocto Project and OpenEmbedded are very welcome.
	You can read the official [[~~http~~://~~www~~.~~openembedded~~.org/~~wiki~~/~~How_to_submit_a_patch_to_OpenEmbedded Openembedded howto~~]]		You can read the official [[https://docs.yoctoproject.org/dev/contributor-guide/submit-changes.html Yocto contributor-guide]]

	=== Set up git ===		=== Set up git ===

2024-06-27T08:33:34Z

Committing your patch

← Older revision		Revision as of 08:33, 27 June 2024
Line 42:		Line 42:
	* required		* required

	~~Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:~~

	git format-patch -s --subject-prefix="OE-~~core~~][PATCH" -1		In case you are sending patches for meta-openembedded or any layer other than openembedded-core, please add the appropriate prefix so that it is clear which layer the patch is intended to be applied to:

			git format-patch --subject-prefix="meta-oe][PATCH" ...

2013-04-09T14:23:25Z

Committing your patch

← Older revision		Revision as of 14:23, 9 April 2013
Line 43:		Line 43:

	Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:		Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:
	~~git format-patch -s --subject-prefix="oe][meta-oe][PATCH" -1~~

	git format-patch -s --subject-prefix="OE-core][PATCH" -1		git format-patch -s --subject-prefix="OE-core][PATCH" -1

2013-04-09T14:23:08Z

Committing your patch

← Older revision		Revision as of 14:23, 9 April 2013
Line 44:		Line 44:
	Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:		Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:
	git format-patch -s --subject-prefix="oe][meta-oe][PATCH" -1		git format-patch -s --subject-prefix="oe][meta-oe][PATCH" -1

			git format-patch -s --subject-prefix="OE-core][PATCH" -1


	Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)		Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)

2013-04-09T14:10:45Z

Committing your patch

← Older revision		Revision as of 14:10, 9 April 2013
Line 46:		Line 46:

	Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)		Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)

	For multiple commits you can substitute -1 above with -N (where N is the number of commits)		For multiple commits you can substitute -1 above with -N (where N is the number of commits)

2013-04-09T14:10:33Z

Committing your patch

← Older revision		Revision as of 14:10, 9 April 2013
Line 46:		Line 46:

	Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)		Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)
			For multiple commits you can substitute -1 above with -N (where N is the number of commits)


Line 53:		Line 54:

	git send-email --to=openembedded-core@lists.openembedded.org patchfilename		git send-email --to=openembedded-core@lists.openembedded.org patchfilename


	== Community review ==		== Community review ==

2013-01-08T07:43:33Z

← Older revision		Revision as of 07:43, 8 January 2013
Line 5:		Line 5:
	=== Set up git ===		=== Set up git ===

	In this case I have a subscribed the ~~oopenembedded~~-devel mailing list with a gmail.com account and I sign my patch with another account.		In this case I have a subscribed the openembedded-devel mailing list with a gmail.com account and I sign my patch with another account.
	Properly ~~configuring~~ git (using tekkub@gmail.com as an example user)		Properly configure git (using tekkub@gmail.com as an example user)

	On Debian / Ubuntu (Note: Fedora uses `yum` OpenSuse uses zypper or yast)		On Debian / Ubuntu (Note: Fedora uses `yum` OpenSuse uses zypper or yast)
Line 44:		Line 44:
	Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:		Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:
	git format-patch -s --subject-prefix="oe][meta-oe][PATCH" -1		git format-patch -s --subject-prefix="oe][meta-oe][PATCH" -1

			Please substitute "PATCH" with "PATCH v2" if you are submitting a revised version after addressing feedback (or v3, v4 etc.)

2013-01-07T14:02:22Z

← Older revision		Revision as of 14:02, 7 January 2013
Line 44:		Line 44:
	Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:		Please add the appopriate prefix so that it is clear which layer the patch is intended to be applied to:
	git format-patch -s --subject-prefix="oe][meta-oe][PATCH" -1		git format-patch -s --subject-prefix="oe][meta-oe][PATCH" -1


	==== Sending using git-send-email ====		==== Sending using git-send-email ====
Line 52:		Line 53:


			== Community review ==

			Your patch will be sent to the mailing list and should be immediately visible on http://patches.openembedded.org/
	.		.

2013-01-07T13:37:18Z

Sending using git-send-email

← Older revision		Revision as of 13:37, 7 January 2013
Line 49:		Line 49:
	To send just the top commit on your current branch (substitute mailing list address as appropriate):		To send just the top commit on your current branch (substitute mailing list address as appropriate):

	git send-email --to=openembedded-~~devel~~@lists.openembedded.org patchfilename		git send-email --to=openembedded-core@lists.openembedded.org patchfilename



	.		.

2013-01-07T13:24:52Z

Sending using git-send-email

← Older revision		Revision as of 13:24, 7 January 2013
Line 48:		Line 48:

	To send just the top commit on your current branch (substitute mailing list address as appropriate):		To send just the top commit on your current branch (substitute mailing list address as appropriate):
	git send-email --to=openembedded-~~core~~@lists.openembedded.org ~~--confirm=always -M -1~~
			git send-email --to=openembedded-devel@lists.openembedded.org patchfilename



			.