From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: docs@lists.yoctoproject.org,
bitbake-devel@lists.openembedded.org,
quentin.schulz@theobroma-systems.com,
"Simone Weiß" <simone.p.weiss@posteo.com>
Subject: Re: [docs] [bitbake-devel] [PATCH v3] bitbake: doc: Add section for variable context
Date: Thu, 11 Apr 2024 14:56:23 +0100 [thread overview]
Message-ID: <d382922b9ddb829c370c09bb5ece65eacbb8cb4f.camel@linuxfoundation.org> (raw)
In-Reply-To: <7ebe5ceb-e3c1-4c66-b080-cbfd3b2cfe80@bootlin.com>
On Thu, 2024-04-11 at 15:34 +0200, Michael Opdenacker wrote:
> Hi Richard
> > Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> >
> > A section on task context would be nice but it can come up in a
> > later
> > patch I guess.
> >
> > Thanks!
> >
> > By the way, I had an old doc build lying around and just git pull
> > my
> > local branch + applying this patch and somehow the navbar was not
> > updated to contain this new section, I had to remove the build dir
> > and
> > compile it from scratch. I'm wondering if we aren't missing
> > something
> > somewhere so that this navbar is updated whenever it needs to?
> >
> > Cheers,
> > Quentin
>
>
> Ping for this nice patch from Simone.
> Both of us have given it our "Reviewed-by".
I think I misread Quentin's comment, sorry. I've merged it now.
Cheers,
Richard
prev parent reply other threads:[~2024-04-11 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 19:20 [PATCH v3] bitbake: doc: Add section for variable context simone.p.weiss
2024-02-26 14:16 ` [bitbake-devel] " Michael Opdenacker
2024-02-27 16:38 ` [docs] " Quentin Schulz
2024-04-11 13:34 ` Michael Opdenacker
2024-04-11 13:56 ` 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:
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=d382922b9ddb829c370c09bb5ece65eacbb8cb4f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=quentin.schulz@theobroma-systems.com \
--cc=simone.p.weiss@posteo.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 read-only IMAP folder(s) and NNTP newsgroup(s).