All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <ernestvanhoecke@gmail.com>, <bitbake-devel@lists.openembedded.org>
Cc: "Alexander Kanavin" <alex@linutronix.de>,
	<docs@lists.yoctoproject.org>,
	"Ernest Van Hoecke" <ernest.vanhoecke@toradex.com>
Subject: Re: [bitbake-devel] [PATCH 2/2] bitbake-setup: write notes for generated build configs
Date: Mon, 01 Jun 2026 09:05:17 +0200	[thread overview]
Message-ID: <DIXISSZ5047B.PSMH6SMC4CF8@bootlin.com> (raw)
In-Reply-To: <20260529-bb-setup-notes-v1-2-a251ef1c5af4@toradex.com>

On Fri May 29, 2026 at 5:00 PM CEST, Ernest Van Hoecke via lists.openembedded.org wrote:
> From: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
>
> For bb-layers configurations, bitbake-setup currently writes an empty
> "conf-notes.txt". Configurations using "oe-template" get this file from
> the template.
>
> Add an optional field called "notes" to configurations that populates
> this field when "bb-layers" is used instead of "oe-template".

Suggestion: call the field "conf-notes" so it matches the resulting filename?

Also, I supposed newlines must be explicitly written in the string ("\n")? Are
those properly converted, or does it need escaping of some sorts?

Thanks,
Antonin


  parent reply	other threads:[~2026-06-01  7:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 14:59 [PATCH 0/2] bitbake-setup: clarify configuration merging and add a notes property Ernest Van Hoecke
2026-05-29 15:00 ` [PATCH 1/2] bitbake-setup: clarify configuration merging Ernest Van Hoecke
2026-05-29 16:47   ` [bitbake-devel] " Alexander Kanavin
2026-05-29 15:00 ` [PATCH 2/2] bitbake-setup: write notes for generated build configs Ernest Van Hoecke
2026-05-29 17:01   ` [bitbake-devel] " Alexander Kanavin
2026-06-01  7:05   ` Antonin Godard [this message]
2026-06-01  8:35     ` [docs] " Alexander Kanavin
2026-06-01 12:53     ` Ernest Van Hoecke
2026-06-01 13:30       ` Alexander Kanavin
2026-06-01 13:55         ` Ernest Van Hoecke
2026-06-01 14:09           ` Alexander Kanavin

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=DIXISSZ5047B.PSMH6SMC4CF8@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=alex@linutronix.de \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=ernest.vanhoecke@toradex.com \
    --cc=ernestvanhoecke@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.