From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <patrick.vogelaar.dev@mailbox.org>
Cc: <openembedded-core@lists.openembedded.org>, <paul@pbarker.dev>
Subject: Re: [OE-core] [PATCH v2] openssh: add variable for key path
Date: Mon, 02 Feb 2026 10:46:35 +0100 [thread overview]
Message-ID: <DG4DPH1SFNO8.1TC9B1KGGAS56@bootlin.com> (raw)
In-Reply-To: <1439731459.127966.1769853692567@app.mailbox.org>
Hi,
On Sat Jan 31, 2026 at 11:01 AM CET, Patrick Vogelaar via lists.openembedded.org wrote:
[...]
>> Thanks for the patch, it was merged in master. As a follow-up, could you
>> send patches to document these variables in
>> https://git.yoctoproject.org/yocto-docs/tree/documentation/ref-manual/variables.rst?
>>
>> And add a note here
>> https://git.yoctoproject.org/yocto-docs/tree/documentation/migration-guides/release-notes-6.0.rst#n24?
>
> I will send a patch that documents the variable. But I don't know where to put it in the release notes. Can you guide me to the section where this would fit in.
Yes, it should be in this document:
https://git.yoctoproject.org/yocto-docs/tree/documentation/migration-guides/release-notes-6.0.rst
Under the bullet point "New variables"
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-02-02 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 11:27 [PATCH] openssh: add variable for key path Patrick Vogelaar
2026-01-08 14:00 ` [OE-core] " Paul Barker
2026-01-25 9:15 ` [PATCH v2] " Patrick Vogelaar
2026-01-29 11:17 ` [OE-core] " Antonin Godard
2026-01-31 10:01 ` patrick.vogelaar.dev
2026-02-02 9:46 ` Antonin Godard [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=DG4DPH1SFNO8.1TC9B1KGGAS56@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.vogelaar.dev@mailbox.org \
--cc=paul@pbarker.dev \
/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