archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <>
To: Paul Eggleton <>,
Subject: Re: [bitbake-devel] [PATCH 0/3] BitBake user manual updates for 2.4
Date: Sat, 22 Apr 2023 10:33:11 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, 2023-04-22 at 15:05 +1200, Paul Eggleton wrote:
> Documentation updates for the 2.4 branch / master (to correspond with
> the Yocto Project 4.2 release).

Thanks for catching these. I wish we could do a better job as we go
along but it is hard with the resources we have. Sadly I'm probably
guilty of not adding some of these.

> here without pointers from the Yocto reference manual currently, since they
> are highly specialized.

I agree that makes sense as those are only really meant to be used by
the core.



      parent reply	other threads:[~2023-04-22  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22  3:05 [PATCH 0/3] BitBake user manual updates for 2.4 Paul Eggleton
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 ` Richard Purdie [this message]

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:

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

  git send-email \ \ \ \ \ \

* 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).