Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Stephen Arnold <stephen.arnold42@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-openembedded/meta-webserver][PATCH] nginx: new recipe, updated from aging original in rpi layer (has not been scrubbed for any potential policy issues).
Date: Fri, 11 Oct 2013 10:19:59 +0100	[thread overview]
Message-ID: <5641383.zhBarnGleb@helios> (raw)
In-Reply-To: <CAOLEWZVgW5g7pKpogBfwPWMw34e27iqk3DHxbeLjFTWBG8Z7YQ@mail.gmail.com>

Hi Steve,

On Thursday 10 October 2013 20:02:49 Stephen Arnold wrote:
> Anyway, I was (somewhat blindly) following the submission/patch
> instructions here:
> 
> http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
> 
> I can certainly provide more info (as well as clean up the recipe) but your
> first few points don't seem to be mentioned there, although the page seems
> fairly current date-wise.  Should I be looking in a different place?

To be honest we probably don't have one place where all of this is currently 
documented, sorry about that. We do have:

 http://www.openembedded.org/wiki/Styleguide

However that doesn't actually cover all of the items I mentioned. Some of the 
material from the following page probably should be added to the style guide:

 http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core

We do also have this page; it's linked from the "How to submit a patch" page 
although perhaps not prominently:

 http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

> Otherwise I'll do me best to address everything, it just might take a few
> days (too many work hours lately).

No worries.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-10-11  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  5:33 [meta-openembedded/meta-webserver][PATCH] nginx: new recipe, updated from aging original in rpi layer (has not been scrubbed for any potential policy issues) stephen.arnold42
2013-10-09  9:55 ` Paul Eggleton
2013-10-11  3:02   ` Stephen Arnold
2013-10-11  9:19     ` Paul Eggleton [this message]
2013-10-17 23:21   ` Stephen Arnold
2013-10-17 23:34     ` Paul Eggleton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5641383.zhBarnGleb@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=stephen.arnold42@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox