Push patches upstream - Revision history

Rpurdie at 10:40, 7 November 2012

2012-11-07T10:40:45Z

← Older revision		Revision as of 10:40, 7 November 2012
Line 1:		Line 1:
	= ~~Outline~~ =		= Sourcing Patches =

	~~OE has quite many patches that are just too valuable to keep to~~		When you encounter problems with software, we're often not alone. For this reason its worth looking at other projects and seeing if they already have solved the problem (as well as checking if there is already a fix upstream). Good sources for patches are:
	~~ourselves~~. ~~OE encourages~~ the ~~following soft policy~~ for ~~adding~~ patches
	~~to the repository.~~

	~~By the way,~~ [http://patch-tracker.debian.org/ Debian], [http://patches.ubuntu.com/ Ubuntu], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] ~~as well as~~ [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] ~~are of course always a great source for grabbing high-quality patches to include in OE.~~		* [http://patch-tracker.debian.org/ Debian]
			* [http://patches.ubuntu.com/ Ubuntu]
			* [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo]
			* [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora]

	= ~~Policy~~ =		= Patch Guidelines =

	~~1) first line~~ in a patch ~~starts with '''upstream:''' and goes on to list~~ the		Experience shows that whilst its clear in your mind why a patch is being added at the time you add a patch, if you revisit it a year later you probably won't remember all the details. For this reason, we ask that patches clearly state some basic information. The full details are available at [[Commit_Patch_Message_Guidelines]].
	~~URL where the bug has been reported upstream or "OE-only"~~ if the ~~patch~~
	~~is just a hack or applicable only to OE~~.
	~~2) further~~ information ~~can optionally be listed in the following fields~~.
	~~Adding them is strongly encouraged where appropriate~~.

	* status: pending, accepted in XXX, rejected (upstream)
	* origin: where the patch has been stolen ;-)
	* comment: any further detail such as description or reason for
	~~application of the patch~~

	~~Take a look at [http://cgit.openembedded.org/cgit.cgi?url~~=~~openembedded/tree/recipes/busybox/busybox-1.9.2/adduser-longops.patch an example]~~		= Sending Patches Upstream =

	= Push'em-weekends =		OE has many patches which for many reasons would be best submitted to the upstream projects rather than being maintained in OE itself. By doing this the wider community can benefit from the changes, recipe upgrading becomes easier and it also in many cases educates the upstream software projects about how their software gets used and for example, the challenges of a cross compile environment.

			== Push'em-weekends ==

	These are sprints in the spirit of our [[bug days\|bug-squashing weekends]] when we try to		These are sprints in the spirit of our [[bug days\|bug-squashing weekends]] when we try to
Line 40:		Line 34:
	to the most recent version of the package in OE.		to the most recent version of the package in OE.

	= sample text for upstream reports =		== sample text for upstream reports ==

	Hi,		Hi,

Eric: Undo revision 3292 by Yjytalamago (Talk)

2010-11-24T07:49:03Z

Undo revision 3292 by Yjytalamago (Talk)

← Older revision	Revision as of 07:49, 24 November 2010
(No difference)

83.171.164.148: UNSPAM:Undo revision 2358 by 77.47.162.103 (Talk)

2010-07-13T08:57:36Z

UNSPAM:Undo revision 2358 by 77.47.162.103 (Talk)

← Older revision		Revision as of 08:57, 13 July 2010
Line 63:		Line 63:

	[[Category:Policy]]		[[Category:Policy]]

	~~[http://www.resumesplanet.com professional resumes]~~

77.47.162.103 at 13:41, 28 June 2010

2010-06-28T13:41:50Z

← Older revision		Revision as of 13:41, 28 June 2010
Line 63:		Line 63:

	[[Category:Policy]]		[[Category:Policy]]

			[http://www.resumesplanet.com professional resumes]

Laibsch: /* Outline */

2010-01-15T18:51:23Z

Outline

← Older revision		Revision as of 18:51, 15 January 2010
Line 5:		Line 5:
	to the repository.		to the repository.

	By the way, [http://patch-tracker.debian.org/ Debian], [[http://patches.ubuntu.com/ Ubuntu]], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.		By the way, [http://patch-tracker.debian.org/ Debian], [http://patches.ubuntu.com/ Ubuntu], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.

	= Policy =		= Policy =

Laibsch at 18:51, 15 January 2010

2010-01-15T18:51:04Z

← Older revision		Revision as of 18:51, 15 January 2010
Line 5:		Line 5:
	to the repository.		to the repository.

	By the way, [http://patch-tracker.debian.org/ Debian], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.		By the way, [http://patch-tracker.debian.org/ Debian], [[http://patches.ubuntu.com/ Ubuntu]], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.

	= Policy =		= Policy =

Laibsch: /* Policy */

2010-01-15T13:18:02Z

Policy

← Older revision		Revision as of 13:18, 15 January 2010
Line 9:		Line 9:
	= Policy =		= Policy =

	1) first line in a patch starts with upstream: and goes on to list the		1) first line in a patch starts with '''upstream:''' and goes on to list the
	URL where the bug has been reported upstream or "OE-only" if the patch		URL where the bug has been reported upstream or "OE-only" if the patch
	is just a hack or applicable only to OE.		is just a hack or applicable only to OE.

Laibsch: /* Outline */

2010-01-13T20:46:50Z

Outline

← Older revision		Revision as of 20:46, 13 January 2010
Line 4:		Line 4:
	ourselves. OE encourages the following soft policy for adding patches		ourselves. OE encourages the following soft policy for adding patches
	to the repository.		to the repository.

			By the way, [http://patch-tracker.debian.org/ Debian], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.

	= Policy =		= Policy =

Laibsch: /* Push'em-weekends */

2009-06-07T01:48:11Z

Push'em-weekends

← Older revision		Revision as of 01:48, 7 June 2009
Line 31:		Line 31:
	list of patches still in need of being documented in line with above policy.		list of patches still in need of being documented in line with above policy.

	find ~~packages~~/ $ -name '.patch' -or -name '.diff' $ -print0\|xargs -0 egrep -vl \^upstream\:		find recipes/ $ -name '.patch' -or -name '.diff' $ -print0 \| xargs -0 egrep -L \^upstream\:

	You can push those patches upstream even if you are only a normal user of		You can push those patches upstream even if you are only a normal user of

Cbrake: use *.org URI's for cgit

2009-05-25T12:25:50Z

use *.org URI's for cgit

← Older revision		Revision as of 12:25, 25 May 2009
Line 18:		Line 18:
	application of the patch		application of the patch

	Take a look at [http://cgit.openembedded.~~net~~/cgit.cgi?url=openembedded/tree/recipes/busybox/busybox-1.9.2/adduser-longops.patch an example]		Take a look at [http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/busybox/busybox-1.9.2/adduser-longops.patch an example]

	= Push'em-weekends =		= Push'em-weekends =
Line 48:		Line 48:
	openembedded.org project did to the sources you publish.		openembedded.org project did to the sources you publish.

	Patch: http://cgit.openembedded.~~net~~/cgit.cgi?url=openembedded/tree/recipes/$project/$patch-url		Patch: http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/$patch-url
	Comment: $explanation		Comment: $explanation

	You can find all our patches for $project at		You can find all our patches for $project at
	http://cgit.openembedded.~~net~~/cgit.cgi?url=openembedded/tree/recipes/$project/		http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/

	Thank you again for your work.		Thank you again for your work.