[poky] [PATCH V3] README: Clarify where to send patches

[Khem Raj]

On Tue, Aug 21, 2012 at 9:27 AM, Darren Hart <dvhart at linux.intel.com> wrote:
> There is still a great deal of confusion over where patches for the
> various components of the poky repository should be sent. Attempt to
> mitigate this by including a blurb in the poky README similar to what
> other layers and repositories do.
>
> V2: Call out the special care required when dealing with the scripts
>     directory per Saul Wold's recommendation.
>
> V3: Recommend applying patches to oe-core prior to sending patches to
>     the oe-core mailing list.
>
> Signed-off-by: Darren Hart <dvhart at linux.intel.com>
> CC: Richard Purdie <richard.purdie at intel.com>
> CC: Paul Gortmaker <paul.gortmaker at windriver.com>
> CC: Paul Eggleton <paul.eggleton at linux.intel.com>
> CC: Khem Raj <raj.khem at gmail.com>
> ---
>  README | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
>
> diff --git a/README b/README
> index 06b1ea6..5084853 100644
> --- a/README
> +++ b/README
> @@ -27,3 +27,23 @@ DISTRO = "") and contains only emulated machine support.
>  For information about OpenEmbedded, see the OpenEmbedded website:
>      http://www.openembedded.org/
>
> +Where to Send Patches
> +=====================
> +
> +As Poky is an integration repository, patches against the various components
> +should be sent to their respective upstreams.
> +
> +bitbake:
> +    bitbake-devel at lists.openembedded.org
> +
> +meta-yocto:
> +    poky at yoctoproject.org
> +
> +Most everything else should be sent to the OpenEmbedded Core mailing list.  If
> +in doubt, check the oe-core git repository for the content you intend to modify.
> +Before sending, be sure the patches apply cleanly to the current oe-core git
> +repository.
> +    openembedded-core at lists.openembedded.org
> +
> +Note: The scripts directory should be treated with extra care as it is a mix
> +      of oe-core and poky-specific files.


Looks good.


> --
> 1.7.11.2
>