From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Jakub Kicinski <kuba@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] docs: submitting-patches: Add Sponsored-by tag to give credits to who sponsored the patch
Date: Thu, 24 Aug 2023 01:24:43 +0200 [thread overview]
Message-ID: <0a2c9daf-c301-8683-9af5-c64ce5d516ca@benettiengineering.com> (raw)
In-Reply-To: <20230821075723.17944dcb@kernel.org>
Hello Jacub, All,
On 21/08/23 16:57, Jakub Kicinski wrote:
> On Mon, 21 Aug 2023 09:40:59 +0200 Geert Uytterhoeven wrote:
>> Personally, I would respond "I'm sorry, but the only advertising
>> space we offer are Copyright headers (for employees) and
>> "user+customer@..." or "name (customer) user@..." (for contractors).
>
> +1
>
>> And this is a separate tag, so it's harder for the analysis tools
>> (whose output your customers must be interested in, too?) to
>> match the tag to the actual Author/Reviewer/...
>
> I think that's a key point. Having a separate tag denote the sponsor
> would make analysis a lot harder. We'd need to start writing parsers
> with much more context awareness.
yes. There are already 2 ways to give credits I was not aware and I
will go with one of those.
Thank you for replying
Best regards
--
Giulio Benetti
CEO&CTO@Benetti Engineering sas
next prev parent reply other threads:[~2023-08-23 23:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 22:09 [RFC PATCH 0/1] Attempt to add Sponsored-by tag Giulio Benetti
2023-08-17 22:09 ` [RFC PATCH 1/1] docs: submitting-patches: Add Sponsored-by tag to give credits to who sponsored the patch Giulio Benetti
2023-08-17 23:23 ` Laurent Pinchart
2023-08-18 0:21 ` Matthew Wilcox
2023-08-19 20:44 ` Giulio Benetti
2023-08-21 8:29 ` Jani Nikula
2023-08-21 12:07 ` Matthew Wilcox
2023-08-21 12:15 ` Jani Nikula
2023-08-21 12:57 ` Matthew Wilcox
2023-08-21 14:38 ` Jani Nikula
2023-08-23 23:29 ` Giulio Benetti
2023-08-19 20:39 ` Giulio Benetti
2023-08-21 7:40 ` Geert Uytterhoeven
2023-08-21 9:27 ` Toke Høiland-Jørgensen
2023-08-23 23:21 ` Giulio Benetti
2023-08-21 14:57 ` Jakub Kicinski
2023-08-23 23:24 ` Giulio Benetti [this message]
2023-08-23 23:19 ` Giulio Benetti
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=0a2c9daf-c301-8683-9af5-c64ce5d516ca@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=kuba@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox