contributor-guide: submit-changes: commit guidelines for recipes

Adding text currently on
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

(From yocto-docs rev: 716756045b75e64846421dcecdd044a06b88052a)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 5 insertions, 0 deletions

diff --git a/documentation/contributor-guide/submit-changes.rst b/documentation/contributor-guide/submit-changes.rst
index 31674d313d..677885e3cf 100644
--- a/documentation/contributor-guide/submit-changes.rst
+++ b/documentation/contributor-guide/submit-changes.rst
@@ -101,6 +101,11 @@ corresponding to each of the patches you will eventually submit.
 See `further guidance <https://www.kernel.org/doc/html/latest/process/submitting-patches.html#separate-your-changes>`__
 in the Linux kernel documentation if needed.
 
+For example, when you intend to add multiple new recipes, each recipe
+should be added in a separate commit. For upgrades to existing recipes,
+the previous version should usually be deleted as part of the same commit
+to add the upgraded version.
+
 #. *Stage Your Changes:* Stage your changes by using the ``git add``
    command on each file you modified. If you want to stage all the
    files you modified, you can even use the ``git add -A`` command.