All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Orling" <ticotimo@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Tim Orling <ticotimo@gmail.com>
Subject: [meta-python2][PATCH v2] README: added recipes must add to packagegroup
Date: Fri, 16 Oct 2020 07:57:55 -0700	[thread overview]
Message-ID: <20201016145755.9147-1-ticotimo@gmail.com> (raw)

When new recipes are added, they must also be
accompanied by a patch adding them to the
packagegroup-meta-python2

This packagegroup is critical to the function of
the CI system behind this layer.

Signed-off-by: Tim Orling <ticotimo@gmail.com>
---
Changes since v1:
  Fix typo of packagroup in gitlog

 README | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README b/README
index e81533e2..a34cbb0c 100644
--- a/README
+++ b/README
@@ -78,6 +78,9 @@ It is expected that ANY upgrades to a recipe will have undergone run-time testin
 the upgrade. Many other developers depend upon the quality of this layer and will be quite upset with
 you when you break their builds.
 
+It is expected that any patch adding a new recipe will also add the recipe to packagegroup-meta-python2.
+This packagegroup is critical to the function of the CI system behind maintenance of this layer.
+
 Commit messages must include a "Signed-off-by:" line, including a valid email address and a legal name
 (not a nickname). The "Signed-off-by:" line means that you are either the author or have the legal right
 to submit the work. Please refer to the "Submitting a patch to OpenEmbedded" [6] and "Commit Patch
-- 
2.25.0


                 reply	other threads:[~2020-10-16 14:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20201016145755.9147-1-ticotimo@gmail.com \
    --to=ticotimo@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 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.