[Buildroot] [PATCH 1/1] docs/manual: add Sponsored-by tag

[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 there are some commit that
include a sort of tag "Sponsored by" without the dash to avoid
scripts/checkpatch.pl to complain but a real standard has not been defined.
With this patch let's try to define a method to give credits consistently.
The goal is to improve contributions from companies or physical persons
that this way should gain visibility in Buildroot and so they should be
more prone to let the work done for them for to be upstreamed.

Signed-off-by: Giulio Benetti <giulio.benetti at benettiengineering.com>
---
 docs/manual/contribute.txt | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
index 94f1c64496..384fdb08c1 100644
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -118,6 +118,11 @@ Acked-by:: Indicates that you code-reviewed the patch and you are
   Reviewed-by is thus mainly that you are prepared to take the blame on
   Acked patches, but not on Reviewed ones.
 
+Sponsored-by:: Indicates that someone sponsored the creation and/or the
+  upstreaming process of the patch. Sponsored-by can contain a company
+  name or a physical person name plus its e-mail the same way it's done
+  for the other tags listed above.
+
 If you reviewed a patch and have comments on it, you should simply reply
 to the patch stating these comments, without providing a Reviewed-by or
 Acked-by tag. These tags should only be provided if you judge the patch
@@ -128,7 +133,7 @@ that testing has been performed. To indicate that you both reviewed and
 tested the patch, provide two separate tags (Reviewed/Acked-by and
 Tested-by).
 
-Note also that _any developer_ can provide Tested/Reviewed/Acked-by
+Note also that _any developer_ can provide Tested/Reviewed/Acked-by/Sponsored-by
 tags, without exception, and we encourage everyone to do this. Buildroot
 does not have a defined group of _core_ developers, it just so happens
 that some developers are more active than others. The maintainer will
-- 
2.34.1