From: Jonathan Corbet <corbet@lwn.net>
To: Dragan Simic <dsimic@manjaro.org>, apw@canonical.com, joe@perches.com
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, dsimic@manjaro.org
Subject: Re: [PATCH v2 0/3] Make Helped-by tag supported
Date: Wed, 06 Nov 2024 07:28:52 -0700 [thread overview]
Message-ID: <87h68k4esb.fsf@trenco.lwn.net> (raw)
In-Reply-To: <cover.1730874296.git.dsimic@manjaro.org>
Dragan Simic <dsimic@manjaro.org> writes:
> This is a short series that adds Helped-by tag to the list of accepted
> tags in scripts/checkpatch.pl, and describes the intended use of this new
> tag in Documentation/process/submitting-patches.rst.
>
> The proposed Helped-by tag fits well to indicate someone had helped with
> the development of a patch, to the level that doesn't warrant providing
> a Co-developed-by tag, but is much more than it would've been indicated
> by providing a Suggested-by tag.
The documentation is meant to cover our existing conventions, rather
than to drive new ones - usually, at least. There are exactly 11
commits in the history with Helped-by, suggesting we're not really at an
established convention at this point. Given that there has been some
resistance to inventing new tags, are we sure that we want this one?
Thanks,
jon
next prev parent reply other threads:[~2024-11-06 14:28 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
2024-11-06 14:28 ` Jonathan Corbet [this message]
2024-11-07 14:09 ` [PATCH v2 0/3] Make Helped-by tag supported 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=87h68k4esb.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=apw@canonical.com \
--cc=dsimic@manjaro.org \
--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;
as well as URLs for NNTP newsgroup(s).