| Message ID | 20251205234033.6363-1-swami310@gmail.com |
|---|---|
| State | Accepted, archived |
| Commit | 652105df57ff0ac433269f7cf19237dd9db81578 |
| Headers | show |
| Series | [v7] bitbake-user-manual: Document BB_CMDLINE | expand |
Hi, I have not heard anything after I submitted Patch V7. Is it accepted ? How can I know the latest status ? Please help me understand. regards Swami On Sat, Dec 6, 2025 at 5:11 AM Swami <swami310@gmail.com> wrote: > Add documentation for the internal read-only variable :term:`BB_CMDLINE`. > > Fixes [YOCTO #15746] > > Signed-off-by: Swaminathan K <swami310@gmail.com> > --- > doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst > b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst > index 734c7858a..32860ec0c 100644 > --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst > +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst > @@ -116,6 +116,10 @@ overview of their function and contents. > Specifies if SSL certificates should be checked when fetching. The > default > value is ``1`` and certificates are not checked if the value is set > to ``0``. > > + :term:`BB_CMDLINE` > + :term:`BB_CMDLINE` is an internal variable and is read-only. It > captures > + the exact command line used for the current invocation of BitBake. > + > :term:`BB_HASH_CODEPARSER_VALS` > Specifies values for variables to use when populating the > codeparser cache. > This can be used selectively to set dummy values for variables to > avoid >
Hi, On Thu Dec 11, 2025 at 6:15 AM CET, Swami via lists.openembedded.org wrote: > Hi, > I have not heard anything after I submitted Patch V7. Is it accepted ? > How can I know the latest status ? > Please help me understand. There is no strict workflow regarding patch statuses on this list. You can refresh the master-next and master branches of bitbake to know whether it is merged or not. A patch being on master-next means it is queued up for testing. If your patch is rejected someone will let you know (but for yours I don't see any apparent reasons). Cheers, Antonin
Le jeu. 11 déc. 2025 à 08:02, Swami via lists.openembedded.org <swami310=gmail.com@lists.openembedded.org> a écrit : > > Hi, > I have not heard anything after I submitted Patch V7. Is it accepted ? How can I know the latest status ? > Please help me understand. Hello, Thanks for your patch :) Your patch is in the master-next branch : https://git.openembedded.org/bitbake/log/?h=master-next Which means it has been selected for review and tests. Once those happen you will either receive a review by mail or see your patch get merged on master. Merges usually happen after the patch review calls (which are on monday and thursday : https://www.yoctoproject.org/community/get-involved/). Ping back if nothing happens in a week or so. > regards > Swami > > On Sat, Dec 6, 2025 at 5:11 AM Swami <swami310@gmail.com> wrote: >> >> Add documentation for the internal read-only variable :term:`BB_CMDLINE`. >> >> Fixes [YOCTO #15746] >> >> Signed-off-by: Swaminathan K <swami310@gmail.com> >> --- >> doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst >> index 734c7858a..32860ec0c 100644 >> --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst >> +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst >> @@ -116,6 +116,10 @@ overview of their function and contents. >> Specifies if SSL certificates should be checked when fetching. The default >> value is ``1`` and certificates are not checked if the value is set to ``0``. >> >> + :term:`BB_CMDLINE` >> + :term:`BB_CMDLINE` is an internal variable and is read-only. It captures >> + the exact command line used for the current invocation of BitBake. >> + >> :term:`BB_HASH_CODEPARSER_VALS` >> Specifies values for variables to use when populating the codeparser cache. >> This can be used selectively to set dummy values for variables to avoid > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#18561): https://lists.openembedded.org/g/bitbake-devel/message/18561 > Mute This Topic: https://lists.openembedded.org/mt/116643097/4316185 > Group Owner: bitbake-devel+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [yoann.congal@smile.fr] > -=-=-=-=-=-=-=-=-=-=-=- >
On Thu, 11 Dec 2025 at 08:50, Yoann Congal via lists.openembedded.org <yoann.congal=smile.fr@lists.openembedded.org> wrote: > > I have not heard anything after I submitted Patch V7. Is it accepted ? How can I know the latest status ? > > Please help me understand. > > Your patch is in the master-next branch : > https://git.openembedded.org/bitbake/log/?h=master-next > > Which means it has been selected for review and tests. Once those > happen you will either receive a review by mail or see your patch get > merged on master. > Merges usually happen after the patch review calls (which are on > monday and thursday : > https://www.yoctoproject.org/community/get-involved/). > Ping back if nothing happens in a week or so. While the process description is correct, all of this has already happened, and the patch landed in master some days ago. Which can be seen in the link above! It's just that master and master-next are the same at the moment. There are no separate notifications for when patches are accepted, you just need to check the upstream branches, either get the latest commits with git locally, or look at the commit log in a browser. Alex
Thanks a lot for the clarifications. This has been one huge learning journey for me. I will start working on the next bug :) regards Swami On Thu, Dec 11, 2025 at 2:21 PM Alexander Kanavin <alex.kanavin@gmail.com> wrote: > On Thu, 11 Dec 2025 at 08:50, Yoann Congal via lists.openembedded.org > <yoann.congal=smile.fr@lists.openembedded.org> wrote: > > > I have not heard anything after I submitted Patch V7. Is it accepted > ? How can I know the latest status ? > > > Please help me understand. > > > > Your patch is in the master-next branch : > > https://git.openembedded.org/bitbake/log/?h=master-next > > > > Which means it has been selected for review and tests. Once those > > happen you will either receive a review by mail or see your patch get > > merged on master. > > Merges usually happen after the patch review calls (which are on > > monday and thursday : > > https://www.yoctoproject.org/community/get-involved/). > > Ping back if nothing happens in a week or so. > > While the process description is correct, all of this has already > happened, and the patch landed in master some days ago. Which can be > seen in the link above! It's just that master and master-next are the > same at the moment. > > There are no separate notifications for when patches are accepted, you > just need to check the upstream branches, either get the latest > commits with git locally, or look at the commit log in a browser. > > Alex >
Le jeu. 11 déc. 2025 à 09:58, Swaminathan K <swami310@gmail.com> a écrit : > > Thanks a lot for the clarifications. This has been one huge learning journey for me. > I will start working on the next bug :) Congrats :) > regards > Swami > > On Thu, Dec 11, 2025 at 2:21 PM Alexander Kanavin <alex.kanavin@gmail.com> wrote: >> >> On Thu, 11 Dec 2025 at 08:50, Yoann Congal via lists.openembedded.org >> <yoann.congal=smile.fr@lists.openembedded.org> wrote: >> > > I have not heard anything after I submitted Patch V7. Is it accepted ? How can I know the latest status ? >> > > Please help me understand. >> > >> > Your patch is in the master-next branch : >> > https://git.openembedded.org/bitbake/log/?h=master-next >> > >> > Which means it has been selected for review and tests. Once those >> > happen you will either receive a review by mail or see your patch get >> > merged on master. >> > Merges usually happen after the patch review calls (which are on >> > monday and thursday : >> > https://www.yoctoproject.org/community/get-involved/). >> > Ping back if nothing happens in a week or so. >> >> While the process description is correct, all of this has already >> happened, and the patch landed in master some days ago. Which can be >> seen in the link above! It's just that master and master-next are the >> same at the moment. *facepalm* I really should refrain from doing anything before my morning coffee... I totally missed that. >> >> There are no separate notifications for when patches are accepted, you >> just need to check the upstream branches, either get the latest >> commits with git locally, or look at the commit log in a browser. >> >> Alex
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst index 734c7858a..32860ec0c 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst @@ -116,6 +116,10 @@ overview of their function and contents. Specifies if SSL certificates should be checked when fetching. The default value is ``1`` and certificates are not checked if the value is set to ``0``. + :term:`BB_CMDLINE` + :term:`BB_CMDLINE` is an internal variable and is read-only. It captures + the exact command line used for the current invocation of BitBake. + :term:`BB_HASH_CODEPARSER_VALS` Specifies values for variables to use when populating the codeparser cache. This can be used selectively to set dummy values for variables to avoid
Add documentation for the internal read-only variable :term:`BB_CMDLINE`. Fixes [YOCTO #15746] Signed-off-by: Swaminathan K <swami310@gmail.com> --- doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst | 4 ++++ 1 file changed, 4 insertions(+)