Lines Matching refs:commit
62 commit <https://blog.vmsplice.net/2011/03/how-to-automatically-run-checkpatchpl.html>`__
91 points in the commit history where QEMU doesn't work for reasons
95 documentation. A commit message that mentions "Also, ..." is often a
97 properly splitting patches and writing good commit messages, see `this
146 Write a meaningful commit message
153 QEMU follows the usual standard for git commit messages: the first line
161 commit message (so that the text still shows up nicely with "git show"
164 The body of the commit message is a good place to document why your
167 they don't go into the final commit message). Make sure the body of the
168 commit message can be read in isolation even if the reader's mailer
173 If your patch fixes a commit that is already in the repository, please
174 add an additional line with "Fixes: <at-least-12-digits-of-SHA-commit-id>
175 ("Fixed commit subject")" below the patch description / before your
176 "Signed-off-by:" line in the commit message.
179 with "Resolves: <URL-of-the-bug>" to the commit message, too. Gitlab can
191 Some other tags that are used in commit messages include "Message-Id:"
316 git repository to fetch the original commit.
333 commit just confuses things. If someone else wrote the patch, git will
344 include using ``git commit -s`` or ``git format-patch -s``. For more
439 just point out code style issues or commit message typos. You'll need to
470 your commit message and/or comments in the code explaining why the code
506 previous versions, but not in the commit message itself. In an email
507 formatted as a git patch, the commit message is the part above the ``---``
511 back to look at this commit in git in six months' time. The part below
535 those commit messages by hand to include the Reviewed-by tag, so that in
539 commit message, as well as listing the changes from the previous
579 may further modify your commit, by resolving simple merge conflicts or