Skip to contentSkip to conversation

contributor-guide: add missing links to mailing lists

PATCH In review [email protected] 4 participants 9 messages Aug 9, 2023 – Aug 10, 2023

lore
Share & tools
lore
#0 lore raw

PATCH 1/3 contributor-guide: add missing links to mailing lists

From: Michael Opdenacker <[email protected]>

And fix such a link too.

---
 documentation/contributor-guide/submit-change.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
documentation/contributor-guide/submit-change.rst +3 -2
index ba56e5986d..2555767102 100644
@@ -52,7 +52,7 @@ varies by component:
 
 For changes to other layers hosted in the Yocto Project source
 repositories (i.e. ``yoctoproject.org``) and tools use the
-:yocto_lists:`Yocto Project </g/yocto/>` general mailing list.
+:yocto_lists:`yocto </g/yocto/>` general mailing list.
 
 .. note::
 
@@ -63,7 +63,8 @@ For additional recipes that do not fit into the core Metadata, you
 should determine which layer the recipe should go into and submit the
 change in the manner recommended by the documentation (e.g. the
 ``README`` file) supplied with the layer. If in doubt, please ask on the
-Yocto general mailing list or on the openembedded-devel mailing list.
+:yocto_lists:`yocto </g/yocto/>` general mailing list or on the
+:oe_lists:`openembedded-devel </g/openembedded-devel>` mailing list.
 
 You can also push a change upstream and request a maintainer to pull the
 change into the component's upstream repository. You do this by pushing
Signature · 1 line
2.34.1
#1 lore raw

PATCH 2/3 contributor-guide: add section about why we use mailing lists

From: Michael Opdenacker <[email protected]>

---
 .../contributor-guide/submit-change.rst       | 41 ++++++++++++++++++-
 1 file changed, 40 insertions(+), 1 deletion(-)
documentation/contributor-guide/submit-change.rst +40 -1
index 2555767102..573491ecbc 100644
@@ -8,10 +8,49 @@ Because the system is extremely configurable and flexible, we recognize
 that developers will want to extend, configure or optimize it for their
 specific uses.
 
+.. _ref-why-mailing-lists:
+
+Contributing through mailing lists --- Why not using web-based workflows?
+=========================================================================
+
+Both Yocto Project and OpenEmbedded have many key components that are
+maintained by patches being submitted on mailing lists. We appreciate this
+approach does look a little old fashioned when other workflows are available
+through web technology such as GitHub, GitLab and others. Since we are often
+asked this question, we’ve decided to document the reasons for using mailing
+lists.
+
+One significant factor is that we value peer review. When a change is proposed
+to many of the core pieces of the project, it helps to have many eyes of review
+go over them. Whilst there is ultimately one maintainer who needs to make the
+final call on accepting or rejecting a patch, the review is made by many eyes
+and the exact people reviewing it are likely unknown to the maintainer. It is
+often the surprise reviewer that catches the most interesting issues!
+
+This is in contrast to the "GitHub" style workflow where either just a
+maintainer makes that review, or review is specifically requested from
+nominated people. We believe there is significant value added to the codebase
+by this peer review and that moving away from mailing lists would be to the
+detriment of our code.
+
+We also need to acknowledge that many of our developers are used to this
+mailing list workflow and have worked with it for years, with tools and
+processes built around it. Changing away from this would result in a loss
+of key people from the project, which would again be to its detriment.
+
+The projects are acutely aware that potential new contributors find the
+mailing list approach off-putting and would prefer a point-and-click web GUI.
+Since we don’t believe that can work for us, the project is aiming to ensure
+`patchwork <https://patchwork.yoctoproject.org/>` is available to help track
+patch status and also looking at how tooling can provide more feedback to users
+about patch status. We are looking at tools such as ``patchtest`` to
+test user contributions before they hit the mailing lists and also at better
+documenting how to use such workflows since we recognise that whilst this was
+common knowledge a decade ago, it might not be as familiar now.
+
 Finding a Suitable Mailing List
 ===============================
 
-The Yocto Project uses a mailing list and a patch-based workflow that is
 similar to the Linux kernel but contains important differences. In
 general, there is a mailing list through which you can submit patches. You
 should send patches to the appropriate mailing list so that they can be
Signature · 1 line
2.34.1
#2 lore raw

Re: [docs] [PATCH 2/3] contributor-guide: add section about why we use mailing lists

Quoted 26 lines · Michael Opdenacker via lists.yoctoproject.org

From: Michael Opdenacker <[email protected]>

---
 .../contributor-guide/submit-change.rst       | 41 ++++++++++++++++++-
 1 file changed, 40 insertions(+), 1 deletion(-)
documentation/contributor-guide/submit-change.rst +0 -0
index 2555767102..573491ecbc 100644
@@ -8,10 +8,49 @@ Because the system is extremely configurable and

flexible, we recognize
that developers will want to extend, configure or optimize it for their specific uses.

+.. _ref-why-mailing-lists:

documentation/contributor-guide/submit-change.rst +7 -0
+
+Contributing through mailing lists --- Why not using web-based workflows?
+=========================================================================
+
+Both Yocto Project and OpenEmbedded have many key components that are
+maintained by patches being submitted on mailing lists. We appreciate this
+approach does look a little old fashioned when other workflows are
Quoted 6 lines

available
+through web technology such as GitHub, GitLab and others. Since we are often
+asked this question, we’ve decided to document the reasons for using mailing
+lists.

Great to read those lines, I was one of those who asked this question ;)

Quoted 2 lines

+One significant factor is that we value peer review. When a change is

Quoted 14 lines

proposed
+to many of the core pieces of the project, it helps to have many eyes of review
+go over them. Whilst there is ultimately one maintainer who needs to make the
+final call on accepting or rejecting a patch, the review is made by many eyes
+and the exact people reviewing it are likely unknown to the maintainer. It is

documentation/contributor-guide/submit-change.rst +5 -0
+often the surprise reviewer that catches the most interesting issues!
+
+This is in contrast to the "GitHub" style workflow where either just a
+maintainer makes that review, or review is specifically requested from
+nominated people. We believe there is significant value added to the
Quoted 5 lines

codebase
+by this peer review and that moving away from mailing lists would be to the
+detriment of our code.

For notifications, I don't see why the web flow would not allow to send notifications
for changes to a mailing list (I think it can also be made per user profile to receive
notifications for a whole project, an issue, a particular project ... etc)

documentation/contributor-guide/submit-change.rst

Quoted 5 lines
documentation/contributor-guide/submit-change.rst +4 -0
+We also need to acknowledge that many of our developers are used to this
+mailing list workflow and have worked with it for years, with tools and
+processes built around it. Changing away from this would result in a loss
+of key people from the project, which would again be to its detriment.

I'd like to know some of these flow that are plugged on mail, can we insert some
examples in the documentation ?

Quoted 4 lines
documentation/contributor-guide/submit-change.rst +2 -0
+The projects are acutely aware that potential new contributors find the
+mailing list approach off-putting and would prefer a point-and-click web

GUI.

I find the term "point-and-click" a little patronizing, github/gitlab/others web tools
are not just point-and-click machine but highly customizable tool aims at smoothen
the developer work (in term of tracking, viewing diff, forking) and to provide
enhanced user experience.

Quoted 8 lines

+Since we don’t believe that can work for us, the project is aiming to ensure
+patchwork <https://patchwork.yoctoproject.org/> is available to help track
+patch status and also looking at how tooling can provide more feedback to users

documentation/contributor-guide/submit-change.rst +2 -0
+about patch status. We are looking at tools such as ``patchtest`` to
+test user contributions before they hit the mailing lists and also at
Quoted 5 lines

better
+documenting how to use such workflows since we recognise that whilst this was
+common knowledge a decade ago, it might not be as familiar now.

I didn't know patchtest, I'll look at it. I think a big improvement (at least for me) in the review
process would be to some kind of colorized webview of a patch towards the target branch.
Sorry, but , unless I miss some cool feature of my gmail client, I find that view (screenshot join)

far more readable that raw diff by mail, e.g:

(quoted diff) +0 -0

b/meta/classes-recipe/cargo.bbclass
index 3ef0bbbb44..8c0b92df8d 100644

meta/classes-recipe/cargo.bbclass +4 -2
@@ -39,7 +39,12 @@ MANIFEST_PATH ??= "${S}/${CARGO_SRC_DIR}/Cargo.toml"
 
 RUSTFLAGS ??= ""
 BUILD_MODE = "${@['--release', ''][d.getVar('DEBUG_BUILD') == '1']}"
-CARGO_BUILD_FLAGS = "-v --offline --target ${RUST_HOST_SYS} ${BUILD_MODE}
--manifest-path=${MANIFEST_PATH}"
+# --frozen flag will prevent network access (which is required since only
+# the do_fetch step is authorized to access network)
+# and will require an up to date Cargo.lock file.
+# This force the package being built to already ship a Cargo.lock, in the

end
+# this is what we want, at least, for reproducibility of the build. +CARGO_BUILD_FLAGS = "-v --frozen --target ${RUST_HOST_SYS} ${BUILD_MODE} --manifest-path=${MANIFEST_PATH}"

# This is based on the content of CARGO_BUILD_FLAGS and generally will
need to

 # change if CARGO_BUILD_FLAGS changes.
Signature · 1 line
2.34.1
Quoted 23 lines
documentation/contributor-guide/submit-change.rst +1 -2
+
 Finding a Suitable Mailing List
 ===============================
 
-The Yocto Project uses a mailing list and a patch-based workflow that is
 similar to the Linux kernel but contains important differences. In
 general, there is a mailing list through which you can submit patches. You
 should send patches to the appropriate mailing list so that they can be
--

2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#4121):
https://lists.yoctoproject.org/g/docs/message/4121
Mute This Topic: https://lists.yoctoproject.org/mt/100643892/6213388
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#3 lore raw

Re: [docs] [PATCH 2/3] contributor-guide: add section about why we use mailing lists

Quoted 25 lines · Frédéric Martinsons
Quoted 21 lines · Michael Opdenacker via lists.yoctoproject.org

+One significant factor is that we value peer review. When a change is proposed
+to many of the core pieces of the project, it helps to have many eyes of review
+go over them. Whilst there is ultimately one maintainer who needs to make the
+final call on accepting or rejecting a patch, the review is made by many eyes
+and the exact people reviewing it are likely unknown to the maintainer. It is
+often the surprise reviewer that catches the most interesting issues!

(quoted diff) +2 -0
+
+This is in contrast to the "GitHub" style workflow where either

just a
+maintainer makes that review, or review is specifically requested from
+nominated people. We believe there is significant value added to the codebase
+by this peer review and that moving away from mailing lists would be to the

Quoted 8 lines
Quoted 2 lines

+detriment of our code.

For notifications, I don't see why the web flow would not allow to send notifications for changes to a mailing list (I think it can also be made per user profile to receive notifications for a whole project, an issue, a particular project ... etc)

You can make a web interface send notices to an email list, sure, that isn't hard. Someone then replies giving feedback on the mailing list to the patch. What happens to that feedback from the web point of view? This "next step" is where the challenge is.

Patchwork is an attempt to make that match up and it basically shows how hard this is to get right and pair the worlds up like that.

Quoted 12 lines

Quoted 8 lines

+We also need to acknowledge that many of our developers are used to this
+mailing list workflow and have worked with it for years, with tools and
+processes built around it. Changing away from this would result in a loss
+of key people from the project, which would again be to its detriment.

I'd like to know some of these flow that are plugged on mail, can we insert some examples in the documentation ?

You mean document how mailing list patch work flow works?

Quoted 4 lines
Quoted 4 lines

+The projects are acutely aware that potential new contributors find the
+mailing list approach off-putting and would prefer a point-and- click web GUI.

Quoted 8 lines
Quoted 1 line

I find the term "point-and-click" a little patronizing, github/gitlab/others web tools
are not just point-and-click machine but highly customizable tool aims at smoothen the developer work (in term of tracking, viewing diff, forking) and to provide enhanced user experience.

I agree we should tweak the wording.

Quoted 13 lines

Quoted 12 lines

+Since we don’t believe that can work for us, the project is aiming to ensure
+patchwork <https://patchwork.yoctoproject.org/> is available to help track
+patch status and also looking at how tooling can provide more feedback to users
+about patch status. We are looking at tools such as ``patchtest`` to
+test user contributions before they hit the mailing lists and also at better
+documenting how to use such workflows since we recognise that whilst this was

Quoted 8 lines
Quoted 2 lines

+common knowledge a decade ago, it might not be as familiar now.

I didn't know patchtest, I'll look at it. I think a big improvement (at least for me) in the review
process would be to some kind of colorized webview of a patch towards the target branch.

If you make a pull request from the contrib repos, you can see colorized diffs using the web interfaces. You can also see that locally with git itself or tools like gitk too. I do use both the cgit interface and gitk commands at different times.

Quoted 3 lines

Sorry, but , unless I miss some cool feature of my gmail client, I find that view (screenshot join) far more readable that raw diff by mail, e.g:

It does depend upon what you're used to. Personally, I can hand edit or even hand write diff files :/. I'm not saying that is a good idea or a good thing but it is what it is.

Cheers,

Richard

#4 lore raw

Re: [docs] [PATCH 2/3] contributor-guide: add section about why we use mailing lists

Quoted 35 lines · Richard Purdie
Quoted 25 lines · Frédéric Martinsons
Quoted 21 lines · Michael Opdenacker via lists.yoctoproject.org

+One significant factor is that we value peer review. When a change is proposed
+to many of the core pieces of the project, it helps to have many eyes of review
+go over them. Whilst there is ultimately one maintainer who needs to make the
+final call on accepting or rejecting a patch, the review is made by many eyes
+and the exact people reviewing it are likely unknown to the maintainer. It is
+often the surprise reviewer that catches the most interesting issues!

(quoted diff) +2 -0
+
+This is in contrast to the "GitHub" style workflow where either

just a
+maintainer makes that review, or review is specifically requested from
+nominated people. We believe there is significant value added to the codebase
+by this peer review and that moving away from mailing lists would be to the

Quoted 8 lines
Quoted 2 lines

+detriment of our code.

For notifications, I don't see why the web flow would not allow to send notifications for changes to a mailing list (I think it can also be made per user profile to receive notifications for a whole project, an issue, a particular project ... etc)

Quoted 5 lines

You can make a web interface send notices to an email list, sure, that isn't hard. Someone then replies giving feedback on the mailing list to the patch. What happens to that feedback from the web point of view? This "next step" is where the challenge is.

Yes I understand that.

Quoted 15 lines

Patchwork is an attempt to make that match up and it basically shows how hard this is to get right and pair the worlds up like that.

Quoted 12 lines
Quoted 9 lines

+We also need to acknowledge that many of our developers are used to this
+mailing list workflow and have worked with it for years, with tools and
+processes built around it. Changing away from this would result in a loss
+of key people from the project, which would again be to its detriment.

I'd like to know some of these flow that are plugged on mail, can we insert some examples in the documentation ?

Quoted 2 lines

You mean document how mailing list patch work flow works?

No, I do know (or I think I know) how the patch flow works. I talked about the text that says "with tools [...] built around it", I wouls like to know what are these tools.

Quoted 37 lines
Quoted 4 lines
Quoted 4 lines

+The projects are acutely aware that potential new contributors find the
+mailing list approach off-putting and would prefer a point-and- click web GUI.

Quoted 8 lines
Quoted 1 line

I find the term "point-and-click" a little patronizing, github/gitlab/others web tools
are not just point-and-click machine but highly customizable tool aims at smoothen the developer work (in term of tracking, viewing diff, forking) and to provide enhanced user experience.

I agree we should tweak the wording.

Quoted 13 lines
Quoted 13 lines

+Since we don’t believe that can work for us, the project is aiming to ensure
+patchwork <https://patchwork.yoctoproject.org/> is available to help track
+patch status and also looking at how tooling can provide more feedback to users
+about patch status. We are looking at tools such as ``patchtest`` to
+test user contributions before they hit the mailing lists and also at better
+documenting how to use such workflows since we recognise that whilst this was

Quoted 8 lines
Quoted 2 lines

+common knowledge a decade ago, it might not be as familiar now.

I didn't know patchtest, I'll look at it. I think a big improvement (at least for me) in the review
process would be to some kind of colorized webview of a patch towards the target branch.

Quoted 5 lines

If you make a pull request from the contrib repos, you can see colorized diffs using the web interfaces. You can also see that locally with git itself or tools like gitk too. I do use both the cgit interface and gitk commands at different times.

Yes of course, I can see my own patches the way I want. But what about contributions from other that I'd like to read more carefully? I can pick these patches and apply in my local checkout and see them "graphically" but it is an additional step that may be skipped if we directly have them somewhere. I agreed that patchwork have a better look interfaces than mail, but as you said earlier, making the second step (i.e commenting a line, suggesting changes... Etc) is not made in such interface.

Quoted 9 lines
Quoted 4 lines

Sorry, but , unless I miss some cool feature of my gmail client, I find that view (screenshot join) far more readable that raw diff by mail, e.g:

It does depend upon what you're used to. Personally, I can hand edit or even hand write diff files :/. I'm not saying that is a good idea or a good thing but it is what it is.

Yes, I'm aware that it is a matter of taste and habits. I only want to gave my point of view. Thank you very much for your answers.

Quoted 5 lines

Cheers,

Richard

#5 lore raw

Re: [docs] [PATCH 2/3] contributor-guide: add section about why we use mailing lists

In reply to Richard Purdie
Quoted 7 lines · Richard Purdie
Quoted 6 lines

I find the term "point-and-click" a little patronizing, github/gitlab/others web tools
are not just point-and-click machine but highly customizable tool aims at smoothen the developer work (in term of tracking, viewing diff, forking) and to provide enhanced user experience.

I agree we should tweak the wording.

I changed the text to a more neutral "would prefer a web-based GUI". Done directly in master-next.
Thanks for the review!
Michael.

Signature · 3 lines
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#6 lore raw

Re: [docs] [PATCH 2/3] contributor-guide: add section about why we use mailing lists

In reply to [email protected]
Quoted 50 lines · Michael Opdenacker via lists.yoctoproject.org

From: Michael Opdenacker <[email protected]>

---
  .../contributor-guide/submit-change.rst       | 41 ++++++++++++++++++-
  1 file changed, 40 insertions(+), 1 deletion(-)
documentation/contributor-guide/submit-change.rst +34 -0
index 2555767102..573491ecbc 100644
@@ -8,10 +8,49 @@ Because the system is extremely configurable and flexible, we recognize
  that developers will want to extend, configure or optimize it for their
  specific uses.
 
+.. _ref-why-mailing-lists:
+
+Contributing through mailing lists --- Why not using web-based workflows?
+=========================================================================
+
+Both Yocto Project and OpenEmbedded have many key components that are
+maintained by patches being submitted on mailing lists. We appreciate this
+approach does look a little old fashioned when other workflows are available
+through web technology such as GitHub, GitLab and others. Since we are often
+asked this question, we’ve decided to document the reasons for using mailing
+lists.
+
+One significant factor is that we value peer review. When a change is proposed
+to many of the core pieces of the project, it helps to have many eyes of review
+go over them. Whilst there is ultimately one maintainer who needs to make the
+final call on accepting or rejecting a patch, the review is made by many eyes
+and the exact people reviewing it are likely unknown to the maintainer. It is
+often the surprise reviewer that catches the most interesting issues!
+
+This is in contrast to the "GitHub" style workflow where either just a
+maintainer makes that review, or review is specifically requested from
+nominated people. We believe there is significant value added to the codebase
+by this peer review and that moving away from mailing lists would be to the
+detriment of our code.
+
+We also need to acknowledge that many of our developers are used to this
+mailing list workflow and have worked with it for years, with tools and
+processes built around it. Changing away from this would result in a loss
+of key people from the project, which would again be to its detriment.
+
+The projects are acutely aware that potential new contributors find the
+mailing list approach off-putting and would prefer a point-and-click web GUI.
+Since we don’t believe that can work for us, the project is aiming to ensure
+`patchwork <https://patchwork.yoctoproject.org/>` is available to help track

documentation/contributor-guide/submit-change.rst Because the system is extremely configurable and flexible, we recognize · line 14

Quoted 10 lines
documentation/contributor-guide/submit-change.rst +6 -1
+patch status and also looking at how tooling can provide more feedback to users
+about patch status. We are looking at tools such as ``patchtest`` to
+test user contributions before they hit the mailing lists and also at better
+documenting how to use such workflows since we recognise that whilst this was
+common knowledge a decade ago, it might not be as familiar now.
+
  Finding a Suitable Mailing List
  ===============================
 
-The Yocto Project uses a mailing list and a patch-based workflow that is

Oops

Quoted 14 lines
documentation/contributor-guide/submit-change.rst +0 -1
  similar to the Linux kernel but contains important differences. In
  general, there is a mailing list through which you can submit patches. You
  should send patches to the appropriate mailing list so that they can be
 
 
 
-=-=-=-=-=-=-=-=-=-=-=-

Links: You receive all messages sent to this group.
View/Reply Online (#4121): https://lists.yoctoproject.org/g/docs/message/4121
Mute This Topic: https://lists.yoctoproject.org/mt/100643892/3616718
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#7 lore raw

Re: [docs] [PATCH 2/3] contributor-guide: add section about why we use mailing lists

HI Daniel,

Quoted 75 lines · Daniel Ammann
Quoted 74 lines · Michael Opdenacker via lists.yoctoproject.org

From: Michael Opdenacker <[email protected]>

---
  .../contributor-guide/submit-change.rst       | 41 ++++++++++++++++++-

  1 file changed, 40 insertions(+), 1 deletion(-)
documentation/contributor-guide/submit-change.rst +0 -0
index 2555767102..573491ecbc 100644
@@ -8,10 +8,49 @@ Because the system is extremely configurable and 

flexible, we recognize
  that developers will want to extend, configure or optimize it for their specific uses.
  +.. _ref-why-mailing-lists:

documentation/contributor-guide/submit-change.rst +2 -0
+
+Contributing through mailing lists --- Why not using web-based 

workflows?
+=========================================================================

documentation/contributor-guide/submit-change.rst +3 -0
+
+Both Yocto Project and OpenEmbedded have many key components that are
+maintained by patches being submitted on mailing lists. We 

appreciate this
+approach does look a little old fashioned when other workflows are available
+through web technology such as GitHub, GitLab and others. Since we are often
+asked this question, we’ve decided to document the reasons for using mailing

documentation/contributor-guide/submit-change.rst +3 -0
+lists.
+
+One significant factor is that we value peer review. When a change 

is proposed
+to many of the core pieces of the project, it helps to have many eyes of review
+go over them. Whilst there is ultimately one maintainer who needs to make the
+final call on accepting or rejecting a patch, the review is made by many eyes
+and the exact people reviewing it are likely unknown to the maintainer. It is

documentation/contributor-guide/submit-change.rst +5 -0
+often the surprise reviewer that catches the most interesting issues!
+
+This is in contrast to the "GitHub" style workflow where either just a
+maintainer makes that review, or review is specifically requested from
+nominated people. We believe there is significant value added to the 

codebase
+by this peer review and that moving away from mailing lists would be to the

documentation/contributor-guide/submit-change.rst +3 -0
+detriment of our code.
+
+We also need to acknowledge that many of our developers are used to 

this

documentation/contributor-guide/submit-change.rst +2 -0
+mailing list workflow and have worked with it for years, with tools and
+processes built around it. Changing away from this would result in a 

loss

documentation/contributor-guide/submit-change.rst +4 -0
+of key people from the project, which would again be to its detriment.
+
+The projects are acutely aware that potential new contributors find the
+mailing list approach off-putting and would prefer a point-and-click 

web GUI.
+Since we don’t believe that can work for us, the project is aiming to ensure
+patchwork <https://patchwork.yoctoproject.org/> is available to help track
+patch status and also looking at how tooling can provide more feedback to users

documentation/contributor-guide/submit-change.rst +2 -0
+about patch status. We are looking at tools such as ``patchtest`` to
+test user contributions before they hit the mailing lists and also 

at better
+documenting how to use such workflows since we recognise that whilst

Quoted 14 lines
Quoted 6 lines

this was

documentation/contributor-guide/submit-change.rst +2 -0
+common knowledge a decade ago, it might not be as familiar now.
+

  Finding a Suitable Mailing List
  ===============================
  -The Yocto Project uses a mailing list and a patch-based workflow that is

Oops

Quoted 5 lines

  similar to the Linux kernel but contains important differences. In general, there is a mailing list through which you can submit patches. You should send patches to the appropriate mailing list so that they can be

Oops indeed. Fixed directly in master-next.
Thanks for the review.
Cheers
Michael.

Signature · 3 lines
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#8 lore raw

PATCH 3/3 contributor-guide: add recipe style guide

In reply to [email protected]

From: Michael Opdenacker <[email protected]>

---
 documentation/contributor-guide/index.rst     |   1 +
 .../contributor-guide/recipe-style-guide.rst  | 263 ++++++++++++++++++
 documentation/dev-manual/new-recipe.rst       |  54 +---
 3 files changed, 268 insertions(+), 50 deletions(-)
 create mode 100644 documentation/contributor-guide/recipe-style-guide.rst
documentation/contributor-guide/index.rst +1 -0
index d723854843..7a39f994e2 100644
@@ -20,6 +20,7 @@ this.
 
    identify-component
    submit-defect
+   recipe-style-guide
    submit-change
 
 .. include:: /boilerplate.rst
documentation/contributor-guide/recipe-style-guide.rst new file +263 -0

263 lines not on this page · raw message

documentation/dev-manual/new-recipe.rst +4 -50

60 lines not on this page · raw message

Signature · 1 line
2.34.1