diff options
| author | Eric Engestrom <[email protected]> | 2019-07-19 21:27:44 +0100 |
|---|---|---|
| committer | Eric Engestrom <[email protected]> | 2019-07-19 22:24:28 +0000 |
| commit | e8febd6cba296ead8f94ae87e7d54a3bb7ca50b0 (patch) | |
| tree | 3d3dbd33c00ac347b2873633cb632a9dacd580e7 | |
| parent | 0e34e1a0ce4741797451648ccad6e634eb4e7a37 (diff) | |
docs: simplify `Fixes:` git command
Reviewed-by: Eric Anholt <[email protected]>
Signed-off-by: Eric Engestrom <[email protected]>
| -rw-r--r-- | docs/submittingpatches.html | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index d8b9fc3b643..786af10459e 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -85,7 +85,9 @@ 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>You can produce those fixes lines by running +<pre>git config --global alias.fixes "show -s --pretty='format:Fixes: %h (\"%s\")'"</pre> +once and then using <pre>git 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> |