From: Jonathan Corbet <corbet@lwn.net>
To: trix@redhat.com
Cc: jacobhuisman@kernelthusiast.com, robh@kernel.org,
grandmaster@al2klimov.de, mchehab+huawei@kernel.org,
konstantin@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: process: Add an example for creating a fixes tag
Date: Thu, 23 Jul 2020 14:49:40 -0600 [thread overview]
Message-ID: <20200723144940.38a9669b@lwn.net> (raw)
In-Reply-To: <20200710200115.21176-1-trix@redhat.com>
On Fri, 10 Jul 2020 13:01:15 -0700
trix@redhat.com wrote:
> To make it a little clearer how to create a fixes tag,
> add an example based on the preceeding gitconfig setup.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> Documentation/process/submitting-patches.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index e58b2c541d25..5219bf3cddfc 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -196,6 +196,11 @@ outputting the above style in the ``git log`` or ``git show`` commands::
> [pretty]
> fixes = Fixes: %h (\"%s\")
>
> +An example call::
> +
> + $ git log -1 --pretty=fixes 54a4f0239f2e
> + Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return the number of pages it actually freed")
> +
Sure, why not? Applied, thanks.
jon
prev parent reply other threads:[~2020-07-23 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 20:01 [PATCH] docs: process: Add an example for creating a fixes tag trix
2020-07-23 20:49 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200723144940.38a9669b@lwn.net \
--to=corbet@lwn.net \
--cc=grandmaster@al2klimov.de \
--cc=jacobhuisman@kernelthusiast.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=robh@kernel.org \
--cc=trix@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).