From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Jonathan Corbet <corbet@lwn.net>, workflows@vger.kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: [RFC PATCH 0/1] Attempt to add Sponsored-by tag
Date: Fri, 18 Aug 2023 00:09:56 +0200 [thread overview]
Message-ID: <20230817220957.41582-1-giulio.benetti@benettiengineering.com> (raw)
Hello All,
working as a consultant for some companies it happens to end up in having
patches that the final customer could be reluctant to send upstream for
many reasons. One of these reason is that at the moment he would not gain
visibility except being added in the commit log as Cc: as far as I know.
What I've been pointed to by someone is "Sponsored by:" that is not a real
tag and it's been used not that often, for example here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=73c289bac05919286f8c7e1660fcaf6ec0468363
And as you know better than me:
$ git log --grep="Sponsored by:"
As explained in the commit log of the patch this is an attempt to define a
standard Sponsored-by: tag including a method of acknowledge on sponsor's side.
The goal is to possibly increase upstreamed patches giving the chance to the
sponsors to gain visibility.
I hope someone likes the idea and that someone could help me to improve the
description in the patch because I'm not an English mother language.
Best regards
--
Giulio Benetti
CEO&CTO@Benetti Engineering sas
Giulio Benetti (1):
docs: submitting-patches: Add Sponsored-by tag to give credits to who
sponsored the patch
Documentation/process/submitting-patches.rst | 38 ++++++++++++++++++++
1 file changed, 38 insertions(+)
--
2.34.1
next reply other threads:[~2023-08-17 22:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 22:09 Giulio Benetti [this message]
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
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=20230817220957.41582-1-giulio.benetti@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=corbet@lwn.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).