From: Sean Christopherson <seanjc@google.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
workflows@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Jacob Keller <jacob.e.keller@intel.com>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Subject: Re: [PATCH] checkpatch: allow tags between co-developed-by and their sign-off
Date: Mon, 23 Oct 2023 07:02:46 -0700 [thread overview]
Message-ID: <ZTZ9Bk3-NrK_cVDu@google.com> (raw)
In-Reply-To: <20231023102846.14830-1-przemyslaw.kitszel@intel.com>
+Mateusz
On Mon, Oct 23, 2023, Przemek Kitszel wrote:
> Additional tags between Co-developed-by and corresponding Signed-off-by
> could include Reviewed-by tags collected by Submitter, which is also
> a Co-developer, but should sign-off at the very end of tags provided by
> the Submitter.
...
> Mateusz Polchlopek <mateusz.polchlopek@intel.com> has reported this to me.
Heh, there's a tag for that...
Reported-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
And it's usually a good idea to Cc the reporter in case there are questions they
can help answer.
> @@ -509,16 +509,18 @@ Example of a patch submitted by the From: author::
> Signed-off-by: Second Co-Author <second@coauthor.example.org>
> Signed-off-by: From Author <from@author.example.org>
>
> -Example of a patch submitted by a Co-developed-by: author::
> +Example of a patch submitted by a Co-developed-by: author, who also collected
> +a Reviewed-by: tag posted for earlier version::
>
> From: From Author <from@author.example.org>
>
> <changelog>
>
> Co-developed-by: Random Co-Author <random@coauthor.example.org>
> Signed-off-by: Random Co-Author <random@coauthor.example.org>
> Signed-off-by: From Author <from@author.example.org>
> Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
> + Reviewed-by: Some Reviewer <srev@another.example.org>
> Signed-off-by: Submitting Co-Author <sub@coauthor.example.org>
This is silly. Allowing tags in-between Co-developed-by with Signed-off-by
unnecessarily complicates things, e.g. people already miss/forget the rule about
tightly coupling Co-developed-by with Signed-off-by.
And if we're being super pedantic about chronological history, arguably the
Reviewed-by should come before the Co-developed-by as adding the Reviewed-by is
a (trivial) modification to the patch that was done by the submitter.
next prev parent reply other threads:[~2023-10-23 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 10:28 [PATCH] checkpatch: allow tags between co-developed-by and their sign-off Przemek Kitszel
2023-10-23 14:02 ` Sean Christopherson [this message]
2023-10-24 9:15 ` Przemek Kitszel
2023-10-29 9:35 ` Krzysztof Kozlowski
2023-10-30 9:05 ` Przemek Kitszel
2023-10-23 14:16 ` Lukas Bulwahn
2023-10-23 14:25 ` Joe Perches
2023-10-24 9:15 ` Przemek Kitszel
-- strict thread matches above, loose matches on Subject: below --
2023-10-20 13:21 Przemek Kitszel
2023-10-20 22:34 ` Joe Perches
2023-10-23 9:24 ` Przemek Kitszel
2023-10-24 20:07 ` Joe Perches
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=ZTZ9Bk3-NrK_cVDu@google.com \
--to=seanjc@google.com \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mateusz.polchlopek@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.