diff options
| author | Quentin Schulz <quentin.schulz@cherry.de> | 2025-09-18 12:24:43 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-09-26 16:40:40 +0100 |
| commit | 2e053bfdabd5edf5d14ad75e19efc3d7bb8bd56d (patch) | |
| tree | 076d9dda8c76916049b1363cc133037df16da007 /documentation/dev-manual/temporary-source-code.rst | |
| parent | ee0d39100d3acea8e7afffcba10b031dbc2f8bb5 (diff) | |
| download | poky-2e053bfdabd5edf5d14ad75e19efc3d7bb8bd56d.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: b84903a760350bd118c56ea9ce4e98039edf6e55)
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/temporary-source-code.rst')
0 files changed, 0 insertions, 0 deletions