From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] docs/manual: add section to explain how to give credits to a sponsor
Date: Tue, 26 Sep 2023 10:00:03 +0200 [thread overview]
Message-ID: <8734z1weik.fsf@48ers.dk> (raw)
In-Reply-To: <20230917205107.366824-2-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Sun, 17 Sep 2023 22:51:07 +0200")
>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
> Sometimes it happens that a Company or a Physical Person sponsors the
> creation and/or the upstreaming process of a patch, but at the moment
> there is no way to give credits to it. In Linux they prepend '+sponsor'
> to the e-mail of the contributor in both authorship and commit log tag as
> discussed here[0]. So let's describe in the manual how to do that as a
> standard.
> [0]:
> https://lore.kernel.org/linux-doc/20230817220957.41582-1-giulio.benetti@benettiengineering.com/
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-26 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 20:51 [Buildroot] [PATCH 0/1] docs/manual: document how to give credits to a sponsor Giulio Benetti
2023-09-17 20:51 ` [Buildroot] [PATCH 1/1] docs/manual: add section to explain " Giulio Benetti
2023-09-26 8:00 ` Peter Korsgaard [this message]
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=8734z1weik.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.de_schampheleire@nokia.com \
/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