From: Dragan Simic <dsimic@manjaro.org>
To: apw@canonical.com, joe@perches.com, corbet@lwn.net
Cc: dwaipayanray1@gmail.com, lukas.bulwahn@gmail.com,
workflows@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, wens@csie.org
Subject: Re: [PATCH v2 3/3] docs: submitting-patches: Describe the use of Helped-by tag
Date: Wed, 06 Nov 2024 07:47:01 +0100 [thread overview]
Message-ID: <33204d0882909375801a2b0c74b5354c@manjaro.org> (raw)
In-Reply-To: <55056f4ec0365c67576a1e1e3162b0cfeadd1c6d.1730874296.git.dsimic@manjaro.org>
Hello,
On 2024-11-06 07:28, Dragan Simic wrote:
> Add the description of the intended use of Helped-by tags, which give
> credit
> to the persons who assisted the patch authors in a way that didn't
> actually
> contribute to the patch directly, i.e. at the source-code level.
>
> Suggested-by: Chen-Yu Tsai <wens@csie.org>
> Signed-off-by: Dragan Simic <dsimic@manjaro.org>
> ---
> Documentation/process/submitting-patches.rst | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/process/submitting-patches.rst
> b/Documentation/process/submitting-patches.rst
> index 382c49659cb9..d0d12536ab68 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -452,8 +452,8 @@ as it was propagated to the maintainers and
> ultimately to Linus, with
> the first SoB entry signalling primary authorship of a single author.
>
>
> -When to use Acked-by:, Cc:, and Co-developed-by:
> -------------------------------------------------
> +When to use Acked-by:, Cc:, Co-developed-by:, and Helped-by
> +-----------------------------------------------------------
Oh, now I see that I've missed a colon after Helped-by in the section
title above. :/ Would you like me to send a v3 with the fix, or do you
prefer to fix it by hand before applying the patch?
> The Signed-off-by: tag indicates that the signer was involved in the
> development of the patch, or that he/she was in the patch's delivery
> path.
> @@ -495,6 +495,14 @@ chronological history of the patch insofar as
> possible, regardless of whether
> the author is attributed via From: or Co-developed-by:. Notably, the
> last
> Signed-off-by: must always be that of the developer submitting the
> patch.
>
> +Helped-by: gives attribution to the persons that helped the patch
> authors
> +in a way that didn't directly produce the patch itself. For example,
> someone
> +may provide significant assistance to the authors by researching the
> schematic
> +of a device that the patch addresses, or by providing the patch
> authors with
> +some background information required to develop the patch, while
> contributing
> +no actual source code. As a result of no direct patch authorship, no
> +Signed-off-by: tags are needed together with Helped-by: tags.
> +
> Note, the From: tag is optional when the From: author is also the
> person (and
> email) listed in the From: line of the email header.
next prev parent reply other threads:[~2024-11-06 6:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 6:28 [PATCH v2 0/3] Make Helped-by tag supported Dragan Simic
2024-11-06 6:28 ` [PATCH v2 1/3] checkpatch: " Dragan Simic
2024-11-06 6:28 ` [PATCH v2 2/3] docs: submitting-patches: Reflow one short paragraph Dragan Simic
2024-11-06 6:28 ` [PATCH v2 3/3] docs: submitting-patches: Describe the use of Helped-by tag Dragan Simic
2024-11-06 6:47 ` Dragan Simic [this message]
2024-11-06 14:28 ` [PATCH v2 0/3] Make Helped-by tag supported Jonathan Corbet
2024-11-07 14:09 ` Dragan Simic
2024-11-08 19:12 ` Dan Williams
2024-11-09 3:10 ` Dragan Simic
2024-12-02 15:00 ` Dragan Simic
2024-12-02 17:11 ` Matthew Wilcox
2024-12-04 0:56 ` Shuah Khan
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=33204d0882909375801a2b0c74b5354c@manjaro.org \
--to=dsimic@manjaro.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox