Quentin Schulz 1b7cb8a80c contributor-guide: submit-changes: reword commit message instructions ...

This should hopefully make it clearer what is expected from the
contributor.

This follows my understanding of git-commit(1)[1] where the following is
a git commit message:

"""
git commit title

git commit description
"""

I'm putting the "Fixes [YOCTO" line in "body of the commit message" so
it's understood as being different from the git commit description so
that the note admonition allowing us to have an empty commit description
doesn't apply to the "Fixes [YOCTO" line.

[1] https://www.man7.org/linux/man-pages/man1/git-commit.1.html#DISCUSSION

(From yocto-docs rev: f0f9d40a04cba684a476caaa053b6f24ade9fb99)

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit b84903a760350bd118c56ea9ce4e98039edf6e55)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>

2025-09-30 08:01:59 -07:00

..

identify-component.rst

contributor-guide: identify component: provide link to repositories

2023-08-30 15:54:59 +01:00

index.rst

contributor guide: update instructions for making and sharing changes

2023-08-30 15:54:59 +01:00

recipe-style-guide.rst

Update the documentation for SRCPV

2024-12-23 05:46:32 -08:00

report-defect.rst

contributor guide: call section "Reporting a defect"

2023-08-30 15:54:59 +01:00

submit-changes.rst

contributor-guide: submit-changes: reword commit message instructions

2025-09-30 08:01:59 -07:00