diff options
| author | Quentin Schulz <quentin.schulz@cherry.de> | 2025-09-18 12:24:43 +0200 |
|---|---|---|
| committer | Steve Sakoman <steve@sakoman.com> | 2025-09-30 08:01:59 -0700 |
| commit | 1b7cb8a80c297e7bce9e27bbfbf40f5da50ec39f (patch) | |
| tree | 7cd6d65bed5353a5bf8f664d3a6ce6db0dd81b08 /scripts/tiny | |
| parent | afd75083e90c9e2318f2c9a61635fde47839dcb0 (diff) | |
| download | poky-1b7cb8a80c297e7bce9e27bbfbf40f5da50ec39f.tar.gz | |
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>
Diffstat (limited to 'scripts/tiny')
0 files changed, 0 insertions, 0 deletions