All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Matthew Wilcox <willy@infradead.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.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: Mon, 21 Aug 2023 11:29:27 +0300	[thread overview]
Message-ID: <87ttss7q8o.fsf@intel.com> (raw)
In-Reply-To: <ZN65iiRiSLmXz89k@casper.infradead.org>

On Fri, 18 Aug 2023, Matthew Wilcox <willy@infradead.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@ideasonboard.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@infradead.org>
>
> but you might have (eg)
>
> Laurent Pinchard (Coca-Cola) <laurent.pinchart@ideasonboard.com>
>
> and then when working for another sponsor:
>
> Laurent Pinchard (Ford) <laurent.pinchart@ideasonboard.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

  parent reply	other threads:[~2023-08-21  8:29 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 [this message]
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
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=87ttss7q8o.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=corbet@lwn.net \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.