summaryrefslogtreecommitdiffstats
path: root/documentation/overview-manual
diff options
context:
space:
mode:
authorMichael Opdenacker <michael.opdenacker@bootlin.com>2023-08-11 19:48:33 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-08-30 15:54:59 +0100
commit9bf8250a403e046a0cbd4bea7113b03b33b27cc0 (patch)
treeea8cdebffe5789ec78635b170fad8013518b307d /documentation/overview-manual
parent82533714c148955d4d0bd08e82407c44b3a1f8ae (diff)
downloadpoky-9bf8250a403e046a0cbd4bea7113b03b33b27cc0.tar.gz
contributor guide: update instructions for making and sharing changes
- Shifting the focus to multiple changes instead of just one - Advising to create a branch for changes - Removing unnecessary or too verbose explanations - Adding useful resources and examples (From yocto-docs rev: e7e47121fd979e034f8f40a043912640a6a25a5e) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/overview-manual')
-rw-r--r--documentation/overview-manual/development-environment.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/overview-manual/development-environment.rst b/documentation/overview-manual/development-environment.rst
index 55f34c18da..262d5cb203 100644
--- a/documentation/overview-manual/development-environment.rst
+++ b/documentation/overview-manual/development-environment.rst
@@ -264,7 +264,7 @@ push them into the "contrib" area and subsequently request that the
264maintainer include them into an upstream branch. This process is called 264maintainer include them into an upstream branch. This process is called
265"submitting a patch" or "submitting a change." For information on 265"submitting a patch" or "submitting a change." For information on
266submitting patches and changes, see the 266submitting patches and changes, see the
267":doc:`../contributor-guide/submit-change`" section in the Yocto Project 267":doc:`../contributor-guide/submit-changes`" section in the Yocto Project
268and OpenEmbedded Contributor Guide. 268and OpenEmbedded Contributor Guide.
269 269
270In summary, there is a single point of entry for changes into the 270In summary, there is a single point of entry for changes into the
@@ -330,7 +330,7 @@ Book <https://book.git-scm.com>`__.
330 release to facilitate this workflow. You can find these scripts in 330 release to facilitate this workflow. You can find these scripts in
331 the ``scripts`` folder of the :term:`Source Directory`. For information 331 the ``scripts`` folder of the :term:`Source Directory`. For information
332 on how to use these scripts, see the 332 on how to use these scripts, see the
333 ":ref:`contributor-guide/submit-change:using scripts to push a change upstream and request a pull`" 333 ":ref:`contributor-guide/submit-changes:using scripts to push a change upstream and request a pull`"
334 section in the Yocto Project and OpenEmbedded Contributor Guide. 334 section in the Yocto Project and OpenEmbedded Contributor Guide.
335 335
336- *Patch Workflow:* This workflow allows you to notify the maintainer 336- *Patch Workflow:* This workflow allows you to notify the maintainer
@@ -339,7 +339,7 @@ Book <https://book.git-scm.com>`__.
339 this type of change, you format the patch and then send the email 339 this type of change, you format the patch and then send the email
340 using the Git commands ``git format-patch`` and ``git send-email``. 340 using the Git commands ``git format-patch`` and ``git send-email``.
341 For information on how to use these scripts, see the 341 For information on how to use these scripts, see the
342 ":doc:`../contributor-guide/submit-change`" section in the Yocto Project 342 ":doc:`../contributor-guide/submit-changes`" section in the Yocto Project
343 and OpenEmbedded Contributor Guide. 343 and OpenEmbedded Contributor Guide.
344 344
345Git 345Git