[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <839c1d04000164e27dff9742e3efc3bcff3025b6.camel@perches.com>
Date: Fri, 14 Dec 2018 07:52:15 -0800
From: Joe Perches <joe@...ches.com>
To: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@...aro.org>,
apw@...onical.com, Andrew Morton <akpm@...ux-foundation.org>,
Greg KH <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, niklas.cassel@...aro.org
Subject: Re: [PATCH] checkpatch: add Co-Developed-by to signature tags
On Fri, 2018-12-14 at 14:01 +0100, Jorge Ramirez-Ortiz wrote:
> As per Documentation/process/submitting-patches, Co-developed-by is a
> valid signature.
>
> This commit removes the warning.
Your commit message doesn't match your subject.
A couple variants have been documented and only
one should actually be used.
$ git grep -i co-developed-by Documentation/process/
Documentation/process/5.Posting.rst: - Co-developed-by: states that the patch was also created by another developer
Documentation/process/submitting-patches.rst:12) When to use Acked-by:, Cc:, and Co-Developed-by:
Documentation/process/submitting-patches.rst:A Co-Developed-by: states that the patch was also created by another developer
$ git log --grep="co-developed-by:" -i | \
grep -ohiP "co-developed-by:" | sort | uniq -c | sort -rn
80 Co-developed-by:
40 Co-Developed-by:
So which should it be?
btw: I prefer neither as I think Signed-off-by: is sufficient.
> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@...aro.org>
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -468,6 +468,7 @@ our $logFunctions = qr{(?x:
>
> our $signature_tags = qr{(?xi:
> Signed-off-by:|
> + Co-Developed-by:|
> Acked-by:|
> Tested-by:|
> Reviewed-by:|
Powered by blists - more mailing lists