From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Takayasu Ito <ito@lineo.co.jp>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs][PATCH v6] release-notes-4.1.rst remove bitbake-layers subcommand argument
Date: Thu, 20 Oct 2022 09:35:13 +0200 [thread overview]
Message-ID: <ef49bd1c-1f31-4161-e72c-2e7e7c30ee45@bootlin.com> (raw)
In-Reply-To: <CANNYZj89KMUU5DwmceqOPWK0hn7v6r-_7RV2jRWNqnwwZxBz1Q@mail.gmail.com>
On 10/20/22 09:29, Alexander Kanavin wrote:
> I agree with the change: only the command should be mentioned, and all
> arguments should be left out, even if they're mandatory.
>
> Alex
>
> On Thu, 20 Oct 2022 at 09:28, Takayasu Ito <ito@lineo.co.jp> wrote:
>> Hi Michael
>>
>> The subcommand save-build-conf, which was added at the same time, only
>> contains the subcommand name and no parameters, so we have made a
>> proposal to unify the notation.
>>
>> If "bitbake-layers create-layers-setup destdir" is used, it would be
>> better to use "bitbake-layers save-build-conf layerpath templatename"
>> with the required parameters to unify the notation.
Ok, makes sense, thanks!
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
... and merged into "master-next".
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-10-20 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 6:52 [docs][PATCH v6] release-notes-4.1.rst remove bitbake-layers subcommand argument ito
2022-10-20 6:56 ` Michael Opdenacker
2022-10-20 7:06 ` Michael Opdenacker
2022-10-20 7:28 ` Takayasu Ito
2022-10-20 7:29 ` Alexander Kanavin
2022-10-20 7:35 ` Michael Opdenacker [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=ef49bd1c-1f31-4161-e72c-2e7e7c30ee45@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=ito@lineo.co.jp \
/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