All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: SeongJae Park <sj@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	workflows@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: suggest adding previous version links
Date: Tue, 06 Jan 2026 14:53:19 -0700	[thread overview]
Message-ID: <87v7hecss0.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251225015447.16387-1-sj@kernel.org>

SeongJae Park <sj@kernel.org> writes:

> For review of patches that revisioned multiple times, patch changelogs
> are very useful.  Adding actual links to the previous versions can
> further help the review.  Using such links, reviewers can double check
> the changelog by themselves, and find previous discussions.  Nowadays
> having such links (e.g., lore.kernel.org archive links) is easy and
> reliable.  Suggest adding such links if available.
>
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
>  Documentation/process/submitting-patches.rst | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index 9a509f1a6873..e69d19ad658f 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -805,7 +805,8 @@ not part of the changelog which gets committed to the git tree. It is
>  additional information for the reviewers. If it's placed above the
>  commit tags, it needs manual interaction to remove it. If it is below
>  the separator line, it gets automatically stripped off when applying the
> -patch::
> +patch.  If available, adding links to previous versions of the patch (e.g.,
> +lore.kernel.org archive link) is recommended to help reviewers::
>  
>    <commit message>
>    ...
> @@ -814,6 +815,9 @@ patch::
>    V2 -> V3: Removed redundant helper function
>    V1 -> V2: Cleaned up coding style and addressed review comments
>  
> +  v2: https://lore.kernel.org/bar
> +  v1: https://lore.kernel.org/foo
> +

Applied, thanks.

jon

      reply	other threads:[~2026-01-06 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-25  1:54 [PATCH] docs: submitting-patches: suggest adding previous version links SeongJae Park
2026-01-06 21:53 ` 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=87v7hecss0.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj@kernel.org \
    --cc=workflows@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.