diff options
| author | Eric Anholt <[email protected]> | 2019-07-12 13:36:51 -0700 |
|---|---|---|
| committer | Eric Anholt <[email protected]> | 2019-07-15 16:29:31 -0700 |
| commit | 82dc168f51e35fe878d9d8eec79169dea82a7e34 (patch) | |
| tree | 18afdade579b1f4283242da8d2862d20f6e3bac8 | |
| parent | 1210e8caaffd7dfaa0db2bee2047133c0fe76e13 (diff) | |
docs: Tell people how to easily generate the Fixes lines.
v2: Include '-s' to suppress the diff.
v3: use the git config command (Ken), use < (Eric)
Reviewed-by: Matt Turner <[email protected]> (v1)
Acked-by: Eric Engestrom <[email protected]>
Reviewed-by: Kenneth Graunke <[email protected]>
| -rw-r--r-- | docs/submittingpatches.html | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index 31c00db4f92..d8b9fc3b643 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -85,6 +85,7 @@ noted in the patch comment. For example: <pre> Fixes: d7b3707c612 "util/disk_cache: use stat() to check if entry is a directory" </pre> +<li>You can produce those fixes lines by running <pre>git config --global pretty.fixes 'Fixes: %h ("%s")'</pre> once and then using <pre>git show -s --pretty=fixes <sha1></pre> <li>If there have been several revisions to a patch during the review process, they should be noted such as in this example: <pre> |