From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [bitbake-devel] [PATCH] doc: bitbake-user-manual: fix syntax in example and improve description
Date: Mon, 26 Jul 2021 22:45:27 +0100 [thread overview]
Message-ID: <e6511dbdc13c163b0a9e445eeacde057181a92ac.camel@linuxfoundation.org> (raw)
In-Reply-To: <ee3b6c49-802c-8840-f8f0-5e47bfb51581@bootlin.com>
On Mon, 2021-07-26 at 17:44 +0200, Michael Opdenacker wrote:
> Hi Richard,
>
> On 7/23/21 10:35 AM, Michael Opdenacker wrote:
> >
> > Of course! I was wondering when we are supposed to start updating the
> > documentation. Probably right now, indeed, right?
> >
> > > An example of my scripted conversion run against the manuals is included
> > > in this commit:
> > >
> > > http://git.yoctoproject.org/cgit.cgi/poky-contrib/diff/documentation/ref-manual/variables.rst?h=rpurdie/overrides-convert&id=9ac22a64a4c0ac4640552e90674e6459f0fece9a
> > Where can I find the script (or commands) that you used to modify the
> > documentation?
>
> I found your script from patch messages
> (http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/overrides-convert&id=f7c5c3bbb9bc5d4c4c8f798d64a020a4504542df),
> and it seems to do the job fine. I just had to exclude the migration
> guides, but that's easy to do it manually.
Sounds good and yes, we can just exclude those paths (we could even do that
in the script).
> How shall I proceed? Shall I send a big patch to
> docs@lists.yoctoproject.org for people to review and check that the
> output from your script is right?
We need to get final approval on exactly what we're converting, then yes.
I wanted to ensure you knew this was coming! :)
I'd note there are some _arc overrides in the docs as there as in the metadata
which need manually tweaking. I also spotted some _sh4. Those are rather obscure
and we may want to use a more common example anyway?
Cheers,
Richard
prev parent reply other threads:[~2021-07-26 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 17:10 [PATCH] doc: bitbake-user-manual: fix syntax in example and improve description Michael Opdenacker
2021-07-22 22:14 ` [bitbake-devel] " Richard Purdie
2021-07-23 8:35 ` [docs] " Michael Opdenacker
2021-07-26 21:39 ` Richard Purdie
[not found] ` <16945E9217B4CF53.14473@lists.openembedded.org>
2021-07-26 15:44 ` Michael Opdenacker
2021-07-26 21:45 ` 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=e6511dbdc13c163b0a9e445eeacde057181a92ac.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.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