From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Jon.Mason@arm.com, JPEWhacker@gmail.com,
Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 02/10] contributor-guide: submit-changes: simplify note
Date: Fri, 18 Aug 2023 19:09:57 +0200 [thread overview]
Message-ID: <20230818171005.92381-3-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230818171005.92381-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/contributor-guide/submit-changes.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/documentation/contributor-guide/submit-changes.rst b/documentation/contributor-guide/submit-changes.rst
index 3f6d2db96c..533aab5b83 100644
--- a/documentation/contributor-guide/submit-changes.rst
+++ b/documentation/contributor-guide/submit-changes.rst
@@ -226,9 +226,8 @@ So, for each identified change:
.. note::
- You do not need to provide a more detailed explanation of a
- change if the change is minor to the point of the single line
- summary providing all the information.
+ If the single line summary is enough to describe a simple
+ change, the body of the commit message can be left empty.
- If the change addresses a specific bug or issue that is associated
with a bug-tracking ID, include a reference to that ID in your
--
2.34.1
next prev parent reply other threads:[~2023-08-18 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 17:09 [PATCH 00/10] Further work on the Contributor Manual michael.opdenacker
2023-08-18 17:09 ` [PATCH 01/10] contributor-guide: move to 2nd place in top menu michael.opdenacker
2023-08-18 17:09 ` michael.opdenacker [this message]
2023-08-18 17:09 ` [PATCH 03/10] contributor-guide: identify component: provide link to repositories michael.opdenacker
2023-08-18 17:09 ` [PATCH 04/10] contributor-guide: submit-changes: detail commit and patch creation michael.opdenacker
2023-08-18 17:10 ` [PATCH 05/10] contributor-guide: submit-changes: develop sending patches section michael.opdenacker
2023-08-18 17:10 ` [PATCH 06/10] manuals: README: update list of manuals michael.opdenacker
2023-08-18 17:10 ` [PATCH 07/10] contributor-guide: submit-changes: reorganize and develop sections michael.opdenacker
2023-08-18 17:10 ` [PATCH 08/10] contributor-guide: submit-changes: improvements to mailing lists section michael.opdenacker
2023-08-18 17:10 ` [PATCH 09/10] contributor-guide: submit-changes: commit guidelines for recipes michael.opdenacker
2023-08-18 17:10 ` [PATCH 10/10] contributor-guide: submit-changes: how to request push access to repositories michael.opdenacker
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=20230818171005.92381-3-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=JPEWhacker@gmail.com \
--cc=Jon.Mason@arm.com \
--cc=docs@lists.yoctoproject.org \
/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