[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a2c9daf-c301-8683-9af5-c64ce5d516ca@benettiengineering.com>
Date: Thu, 24 Aug 2023 01:24:43 +0200
From: Giulio Benetti <giulio.benetti@...ettiengineering.com>
To: Jakub Kicinski <kuba@...nel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 1/1] docs: submitting-patches: Add Sponsored-by tag to
give credits to who sponsored the patch
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@...etti Engineering sas
Powered by blists - more mailing lists