From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
<docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 1/2] conf.py: add a bitbake_git extlink
Date: Wed, 30 Oct 2024 11:31:59 +0100 [thread overview]
Message-ID: <D592LMQ2JRAV.2HSI6XNGJR2L2@bootlin.com> (raw)
In-Reply-To: <502402c8-3d16-46b6-b0ca-d2b8d92fd9ff@cherry.de>
Hi Quentin,
On Wed Oct 30, 2024 at 11:21 AM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 10/30/24 10:23 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> To make references to the bitbake repo, add an extlink for it and use it
>> in the docs with ":bitbake_git:`lib/bb/utils.py </tree/lib/bb/utils.py>`".
>>
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>
> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> I believe we could also migrate a few oe_git to bitbake_git now across
> the docs?
>
> git grep 'oe_git.*bitbake' should help you identify those.
Surely, I think there is also a lot of `poky_git` usage while it should be
`oe_git`… I have a note to fix that in my todo. :)
> Thanks!
> Quentin
Thank you,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-10-30 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 9:23 [PATCH 0/2] Document how to provide configuration from layer.conf Antonin Godard
2024-10-30 9:23 ` [PATCH 1/2] conf.py: add a bitbake_git extlink Antonin Godard
2024-10-30 10:21 ` [docs] " Quentin Schulz
2024-10-30 10:31 ` Antonin Godard [this message]
2024-10-30 9:23 ` [PATCH 2/2] dev-manual: document how to provide confs from layer.conf Antonin Godard
2024-10-30 10:18 ` [docs] " Quentin Schulz
2024-10-30 14:32 ` Antonin Godard
2024-10-31 10:13 ` Quentin Schulz
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=D592LMQ2JRAV.2HSI6XNGJR2L2@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--cc=thomas.petazzoni@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