From: Paul Eggleton <bluelightning@bluelightning.org>
To: bitbake-devel@lists.openembedded.org
Cc: michael.opdenacker@bootlin.com
Subject: [PATCH 0/3] BitBake user manual updates for 2.4
Date: Sat, 22 Apr 2023 15:05:20 +1200 [thread overview]
Message-ID: <cover.1682131637.git.bluelightning@bluelightning.org> (raw)
Documentation updates for the 2.4 branch / master (to correspond with
the Yocto Project 4.2 release).
Note: I am electing to add BB_GLOBAL_PYMODULES and BB_HASH_CODEPARSER_VALS
here without pointers from the Yocto reference manual currently, since they
are highly specialized.
The following changes since commit 66131fa6a3e12c28710d09e1dbf3c03f2981280d:
cooker: do not abort on single ctrl-c (2023-04-20 12:36:18 +0100)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib paule/doc-updates-2.4
http://cgit.openembedded.org/bitbake-contrib/log/?h=paule/doc-updates-2.4
Paul Eggleton (3):
bitbake-user-manual: document BB_CACHEDIR
bitbake-user-manual: add addpylib and BB_GLOBAL_PYMODULES
bitbake-user-manual: add BB_HASH_CODEPARSER_VALS
.../bitbake-user-manual-metadata.rst | 18 ++++++++++++++
.../bitbake-user-manual-ref-variables.rst | 24 +++++++++++++++++++
2 files changed, 42 insertions(+)
--
2.34.1
next reply other threads:[~2023-04-22 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 3:05 Paul Eggleton [this message]
2023-04-22 3:05 ` [PATCH 1/3] bitbake-user-manual: document BB_CACHEDIR Paul Eggleton
2023-04-22 3:05 ` [PATCH 2/3] bitbake-user-manual: add addpylib and BB_GLOBAL_PYMODULES Paul Eggleton
2023-04-22 3:05 ` [PATCH 3/3] bitbake-user-manual: add BB_HASH_CODEPARSER_VALS Paul Eggleton
2023-04-22 9:33 ` [bitbake-devel] [PATCH 0/3] BitBake user manual updates for 2.4 Richard Purdie
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=cover.1682131637.git.bluelightning@bluelightning.org \
--to=bluelightning@bluelightning.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=michael.opdenacker@bootlin.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;
as well as URLs for NNTP newsgroup(s).