From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Julien Stephan" <jstephan@baylibre.com>
Cc: <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH v4 2/3] ref-manual: variables: add SIGGEN_LOCKEDSIGS* variables
Date: Wed, 06 Nov 2024 14:39:19 +0100 [thread overview]
Message-ID: <D5F4YVXTS4OS.U94L52CX9NOF@bootlin.com> (raw)
In-Reply-To: <CAEHHSvadv3uyRciqnG2LwxVhRCU=CogZ1EYQof1WbWLJTXZR0g@mail.gmail.com>
On Wed Nov 6, 2024 at 2:34 PM CET, Julien Stephan wrote:
> Le mer. 6 nov. 2024 à 11:30, Antonin Godard
> <antonin.godard@bootlin.com> a écrit :
>>
>> Hi Julien,
>>
>> On Wed Nov 6, 2024 at 10:02 AM CET, Julien Stephan wrote:
>> [...]
>> > + Then you can look at files in ``build/stamps/<arch>/bc`` and search for the
>>
>> Didn't notice before, but it should be ``tmp/stamps/<arch>/bc``, right?
>
> right, I forgot the ``tmp``. Should I use
> ``build/tmp/stamps/<arch>/bc`` or ``tmp/stamps/<arch>/bc`` ?
> I want confirmation to avoid another round ;)
Seems like a lot of places in the docs refer to build/tmp/work/..., so yes,
please include `build/` at the beginning.
Thank you,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-11-06 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 9:02 [PATCH v4 0/3] Add bblock documentation Julien Stephan
2024-11-06 9:02 ` [PATCH v4 1/3] styles: vocabularies: Yocto: add sstate Julien Stephan
2024-11-06 9:02 ` [PATCH v4 2/3] ref-manual: variables: add SIGGEN_LOCKEDSIGS* variables Julien Stephan
2024-11-06 10:30 ` [docs] " Antonin Godard
2024-11-06 13:34 ` Julien Stephan
2024-11-06 13:39 ` Antonin Godard [this message]
2024-11-06 9:02 ` [PATCH v4 3/3] dev-manual: add bblock documentation Julien Stephan
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=D5F4YVXTS4OS.U94L52CX9NOF@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=jstephan@baylibre.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