[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ttss7q8o.fsf@intel.com>
Date: Mon, 21 Aug 2023 11:29:27 +0300
From: Jani Nikula <jani.nikula@...el.com>
To: Matthew Wilcox <willy@...radead.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: Giulio Benetti <giulio.benetti@...ettiengineering.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
On Fri, 18 Aug 2023, Matthew Wilcox <willy@...radead.org> wrote:
> On Fri, Aug 18, 2023 at 02:23:48AM +0300, Laurent Pinchart wrote:
>> Just adding one data point here, without judging on the merits of this
>> proposal. I've been requested previously by customers to increase their
>> visibility in the kernel development statistics, and the way we found to
>> do so was to sign-off patches with
>>
>> Laurent Pinchart <laurent.pinchart+customer@...asonboard.com>
>>
>> (where "customer" is to be replaced with the customer name).
>
> I quite like Sponsored-by: but yet another approach could be the
> same as that used by those of us whole use personal email addresses
> while being employed by someone. So my SoB is:
>
> Matthew Wilcox (Oracle) <willy@...radead.org>
>
> but you might have (eg)
>
> Laurent Pinchard (Coca-Cola) <laurent.pinchart@...asonboard.com>
>
> and then when working for another sponsor:
>
> Laurent Pinchard (Ford) <laurent.pinchart@...asonboard.com>
Just an observation, git shortlog -s/-se groups/distinguishes,
respectively, the author and sponsor in Laurent's approach. Not so with
Matthew's approach.
Probably depends on the POV which approach this favors. ;)
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
Powered by blists - more mailing lists