[Buildroot] [PATCH 0/1] docs/manual: document how to give credits to a sponsor

[Buildroot] [PATCH 0/1] docs/manual: document how to give credits to a sponsor

[Giulio Benetti]

Following my previous patch:
https://patchwork.ozlabs.org/project/buildroot/patch/20230819211825.60854-2-giulio.benetti@benettiengineering.com/

I come up with this after having feedbacks from Linux ML:
https://lore.kernel.org/linux-doc/20230817220957.41582-1-giulio.benetti@benettiengineering.com/

Basically they have 2 ways to give credits to sponsors, but the most used
way that is used a lot by analysis tools is the one prepending '+sponsor'
to developer's e-mail domain.

Best regards
Giulio

Giulio Benetti (1):
  docs/manual: add section to explain how to give credits to a sponsor

 docs/manual/contribute.txt | 7 +++++++
 1 file changed, 7 insertions(+)

-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

[Buildroot] [PATCH 1/1] docs/manual: add section to explain how to give credits to a sponsor

[Giulio Benetti]

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>
---
 docs/manual/contribute.txt | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
index 384fdb08c1..df3e0af4b4 100644
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -147,6 +147,13 @@ Buildroot's Patchwork website can be used to pull in patches for testing
 purposes. Please see xref:apply-patches-patchwork[] for more
 information on using Buildroot's Patchwork website to apply patches.
 
+To give credits to who sponsored the creation of a patch or the process of
+upstreaming it add '+sponsor' before the e-mail domain in autorship and in
+any possible tag listed above. For a company which sponsored:
+"Name Surname <name.surname+companyname@mail.com>"
+or in case of a physical person his name and surname all together:
+"Name Surname <name.surname+namesurname@mail.com>"
+
 [[apply-patches-patchwork]]
 ==== Applying Patches from Patchwork
 
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] docs/manual: add section to explain how to give credits to a sponsor

[Peter Korsgaard]

>>>>> "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