From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <swami310@gmail.com>,
"Michael Opdenacker" <michael.opdenacker@rootcommit.com>
Cc: <bitbake-devel@lists.openembedded.org>, <docs@lists.yoctoproject.org>
Subject: Re: [bitbake-devel] [PATCH v5] bitbake-user-manual: Documenting BB_CMDLINE
Date: Thu, 04 Dec 2025 13:57:14 +0100 [thread overview]
Message-ID: <DEPG6R9444HV.37PEKFWSS5JCP@bootlin.com> (raw)
In-Reply-To: <CA+-_CqnmcJ1txe-AuECK-sJ+N-+itruvAtQAkpNPQh4ckhPFFw@mail.gmail.com>
Hi Swani,
On Thu Dec 4, 2025 at 12:19 PM CET, Swami via lists.openembedded.org wrote:
> Thanks Michael,
> I will do the changes and submit a new patch.
> I picked up documentation assuming it would be easy :)
> Many thanks to you,Antonin, for bearing with my endless patches for such a
> small change.
> On the positive side, I am getting comfortable with the steps by this
> repetition.
> Unfortunately , that is adding to much back and forth
> Hope I can nail it with the next patch.
No problem, that's part of the learning process and once that's settled in,
you'll have less and less iterations on patches. :) We are happy to welcome new
contributors.
I can also suggest b4 which does makes things a bit easier to manage patches:
https://b4.docs.kernel.org/en/latest/
I can't make the modifications locally though, as I don't merge things on the
bitbake (only yocto-docs). Please send a new version of the patch, that's fine!
Thank you,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-12-04 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251204002531.7660-1-swami310@gmail.com>
2025-12-04 10:54 ` [PATCH v5] bitbake-user-manual: Documenting BB_CMDLINE Michael Opdenacker
[not found] ` <CA+-_CqnmcJ1txe-AuECK-sJ+N-+itruvAtQAkpNPQh4ckhPFFw@mail.gmail.com>
2025-12-04 12:57 ` 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=DEPG6R9444HV.37PEKFWSS5JCP@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@rootcommit.com \
--cc=swami310@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox