All of lore.kernel.org
 help / color / mirror / Atom feed
* Patch Comments and Upstream-Status
@ 2011-04-05 19:17 Saul Wold
  2011-04-05 22:17 ` Loïc Minier
  0 siblings, 1 reply; 2+ messages in thread
From: Saul Wold @ 2011-04-05 19:17 UTC (permalink / raw)
  To: Yocto Project Discussion, poky@yoctoproject.org


Yocto Contributors:

Do you ever wonder why a patch exists?  Thought that it should be part 
of the upstream project?

Well now's your chance to help as we move forward with our next release, 
we want to improve the quality of the patch comments and ensure that 
patches that can be included in the upstream projects are. The goal is 
to reduce the total number of patches that we need to carry forward and 
maintain, this will improve the overall quality of the project.

The wiki has been updated to include information about what we would 
like to see in the patch comments, including a format for a new field
Upstream-Status.

When creating new patches, updating existing recipes, please take a few 
minutes to ensure that all the patches have the Upstream-Status field 
and if appropriate start the process of requesting the upstream project 
to accept the patch.

The format and possible status key works are as follows:

Upstream-Status:
Pending
  No determination has been made yet or not yet submitted to upstream
Submitted
  Submitted to upstream, waiting approval
Accepted
  Accepted in upstream, expect it to be removed at next update, include 
expected version info
Backport
  Backported from new upstream version, because we are at a fixed 
version, include upstream version info
Denied
  Not accepted by upstream, include reason in patch
Inappropriate [reason]
  The patch is not appropriate for upstream, include a brief reason on 
the same line enclosed with []
  Reason can be:
	native
	licensing
	enable feature
	disable feature
	bugfix (add bug url here)
	embedded specific
	other (give details in comments)

If you are a maintainer of recipes, please work through your patches and 
submit poky  pull requests and upstream patch submissions.

Wiki Page:

http://wiki.yoctoproject.org/wiki/Best_Known_Methods_%28BKMs%29_for_Package_Updating#Patch_Comments

Please let me know if you have any comments or suggestions to improve 
this process.

Thanks
     Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Patch Comments and Upstream-Status
  2011-04-05 19:17 Patch Comments and Upstream-Status Saul Wold
@ 2011-04-05 22:17 ` Loïc Minier
  0 siblings, 0 replies; 2+ messages in thread
From: Loïc Minier @ 2011-04-05 22:17 UTC (permalink / raw)
  To: yocto

        Hi,

On Tue, Apr 05, 2011, Saul Wold wrote:
> The wiki has been updated to include information about what we would
> like to see in the patch comments, including a format for a new
> field
> Upstream-Status.

 Did you consider using DEP3 patch headers?
 http://dep.debian.net/deps/dep3/

   Cheers,
-- 
Loïc Minier


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-04-05 22:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-05 19:17 Patch Comments and Upstream-Status Saul Wold
2011-04-05 22:17 ` Loïc Minier

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.