workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: apw@canonical.com, joe@perches.com, 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 0/3] Make Helped-by tag supported
Date: Thu, 07 Nov 2024 15:09:02 +0100	[thread overview]
Message-ID: <cabfa180845df30bfb7a541a701a57e9@manjaro.org> (raw)
In-Reply-To: <87h68k4esb.fsf@trenco.lwn.net>

Hello Jonathan,

On 2024-11-06 15:28, Jonathan Corbet wrote:
> 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 for your response.

Of course, the documentation would be updated only if the first patch
in this series becomes accepted, i.e. if Helped-by becomes supported
in checkpatch.pl.  I'm sorry if I wasn't clear enough.

It's usually said that necessity is mother of invention, which is the
case here.  In a few words, I've got another patch pending merging [1]
that a couple of people helped me with.  What they did is more than
what Suggested-by tags would indicate, but doesn't really warrant
Co-developed-by + Signed-off-by pairs or tags.  Having Helped-by tags
provided for both of them would fit pretty much perfectly.

It was very similar, if not the same, when it comes to the development
that led to a few commits already containing Helped-by tags. [2]  Sure,
that isn't a whole lot of such commits, but this may be a good point
to decide what to do with Helped-by tags in the future.

I'm fully aware that we may be reluctant to supporting additional tags,
because we may then end up with a whole bunch of strange tags that might
be a bit hard to understand and use properly, but I think that adding
Helped-by to the supported tag list may actually be a good thing to do.
As described above, Helped-by fits very well between the Suggested-by
tag and the Co-developed-by + Signed-off-by pair of tags, and I think
that providing the right level of attribution may be beneficial.

[1] 
https://lore.kernel.org/linux-sunxi/129f0c754d071cca1db5d207d9d4a7bd9831dff7.1726773282.git.dsimic@manjaro.org/T/#u
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?qt=grep&q=Helped-by

  reply	other threads:[~2024-11-07 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  6:28 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 ` [PATCH v2 0/3] Make Helped-by tag supported Jonathan Corbet
2024-11-07 14:09   ` Dragan Simic [this message]
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=cabfa180845df30bfb7a541a701a57e9@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