Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Paul Eggleton" <paul.eggleton@linux.microsoft.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH v2 01/14] ref-manual: add METADATA_REVISION and METADATA_BRANCH
Date: Thu, 15 Apr 2021 02:58:59 -0700	[thread overview]
Message-ID: <3b80ece864e8cc06f09d3d4ee645ddeef5d4eaf6.1618480508.git.paul.eggleton@linux.microsoft.com> (raw)
In-Reply-To: <cover.1618480508.git.paul.eggleton@linux.microsoft.com>

From: Paul Eggleton <paul.eggleton@microsoft.com>

These are not new variables, but we are using METADATA_REVISION in a new
place and thus need to refer to it.

Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
---
 documentation/ref-manual/variables.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 19f5e34..f906d4e 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -4659,6 +4659,14 @@ system and gives an overview of their function and contents.
    :term:`MAINTAINER`
       The email address of the distribution maintainer.
 
+   :term:`METADATA_BRANCH`
+      The branch currently checked out for the OpenEmbedded-Core layer (path
+      determined by :term:`COREBASE`).
+
+   :term:`METADATA_REVISION`
+      The revision currently checked out for the OpenEmbedded-Core layer (path
+      determined by :term:`COREBASE`).
+
    :term:`MIRRORS`
       Specifies additional paths from which the OpenEmbedded build system
       gets source code. When the build system searches for source code, it
-- 
1.8.3.1


  reply	other threads:[~2021-04-15  9:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  9:58 [PATCH v2 00/14] Documentation updates for 3.3 Paul Eggleton
2021-04-15  9:58 ` Paul Eggleton [this message]
2021-04-15  9:59 ` [PATCH v2 02/14] Use variables for minimum host versions and bump Python to 3.6 Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 03/14] ref-manual: update/fix text for SDK_VERSION Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 04/14] overview-manual: fix git command line Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 05/14] ref-manual: and SDK_CUSTOM_TEMPLATECONF to glossary Paul Eggleton
2021-04-15 10:11   ` [docs] " Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 06/14] ref-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 07/14] ref-manual: add python3targetconfig class and remove python 2 references Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 08/14] ref-manual: add passwd-expire to EXTRA_USERS_PARAMS Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 09/14] ref-manual: add FIT_KERNEL_COMP_ALG* Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 10/14] ref-manual: fix reference to build-essential Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 11/14] ref-manual: tweak buildtools section Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 12/14] ref-manual: add migration section for 3.3 release Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 13/14] ref-manual: migration guide: add release codenames Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 14/14] ref-manual: add mention of DISTUTILS_SETUP_PATH 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=3b80ece864e8cc06f09d3d4ee645ddeef5d4eaf6.1618480508.git.paul.eggleton@linux.microsoft.com \
    --to=paul.eggleton@linux.microsoft.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