From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [kirkstone][PATCH 3/7] ref-manual: variables: add RECIPE_MAINTAINER
Date: Tue, 14 Nov 2023 17:49:38 +0100 [thread overview]
Message-ID: <20231114164942.133472-4-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20231114164942.133472-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/variables.rst | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 5a34ea7856..a75581f2fd 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -6463,6 +6463,22 @@ system and gives an overview of their function and contents.
BitBake User Manual for additional information on tasks and
dependencies.
+ :term:`RECIPE_MAINTAINER`
+ This variable defines the name and e-mail address of the maintainer of a
+ recipe. Such information can be used by human users submitted changes,
+ and by automated tools to send notifications, for example about
+ vulnerabilities or source updates.
+
+ The variable can be defined in a global distribution :oe_git:`maintainers.inc
+ </openembedded-core/tree/meta/conf/distro/include/maintainers.inc>` file::
+
+ meta/conf/distro/include/maintainers.inc:RECIPE_MAINTAINER:pn-sysvinit = "Ross Burton <ross.burton@arm.com>"
+
+ It can also be directly defined in a recipe,
+ for example in the ``libgpiod`` one::
+
+ RECIPE_MAINTAINER = "Bartosz Golaszewski <brgl@bgdev.pl>"
+
:term:`RECIPE_NO_UPDATE_REASON`
If a recipe should not be replaced by a more recent upstream version,
putting the reason why in this variable in a recipe allows
--
2.34.1
next prev parent reply other threads:[~2023-11-14 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 16:49 [kirkstone][PATCH 0/7] kirkstone backports michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 1/7] ref-manual: variables: document OEQA_REPRODUCIBLE_* variables michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 2/7] ref-manual: variables: mention new CDN for SSTATE_MIRRORS michael.opdenacker
2023-11-14 16:49 ` michael.opdenacker [this message]
2023-11-14 16:49 ` [kirkstone][PATCH 4/7] overview-manual: concepts: Add Bitbake Tasks Map michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 5/7] ref-manual: update SDK_NAME variable documentation michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 6/7] ref-manual: classes: explain cml1 class name michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 7/7] manuals: update class references michael.opdenacker
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=20231114164942.133472-4-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox