From: Miklos Vajna <vmiklos@collabora.co.uk>
To: Pranit Bauva <pranit.bauva@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Signed-off-by vs Reviewed-by
Date: Thu, 31 Mar 2016 16:35:02 +0200 [thread overview]
Message-ID: <20160331143501.GE19857@collabora.co.uk> (raw)
In-Reply-To: <CAFZEwPMzcqrd8NEP6MH5saXL2KdUKAyN51uuoS5=aeU0aPWjJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
Hi,
On Thu, Mar 31, 2016 at 07:54:47PM +0530, Pranit Bauva <pranit.bauva@gmail.com> wrote:
> Are you suggesting to use a different email address for commiting,
> signing off and reviewing?
Let's say project A has a workflow where patch authors and maintainers
add a "Signed-off-by: A B <a@example.com>" line. This is well-supported
by git, various commands have a -s option to add that line.
However, if project B has a workflow where patch authors add no such
line, and reviewers add a "Reviewed-by: A B <a@example.com>" line, then
you have to add that line manually when you do a review.
I suggest to give a bit more support to this workflow in git. One way of
doing that would be to make the Signed-off-by string configurable. I can
look into implementing that, but first I wanted to discuss the idea here
on the list -- perhaps there is a better way to support that. :-)
Typing that line (including copy&pasting your name + email all the time)
is a bit boring.
Regards,
Miklos
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-03-31 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 12:35 Signed-off-by vs Reviewed-by Miklos Vajna
2016-03-31 14:24 ` Pranit Bauva
2016-03-31 14:35 ` Miklos Vajna [this message]
2016-03-31 14:57 ` Sidhant Sharma
2016-03-31 15:09 ` Christian Couder
2016-03-31 16:28 ` Junio C Hamano
2016-03-31 17:21 ` Jeff King
2016-03-31 17:23 ` Junio C Hamano
2016-04-01 14:10 ` Miklos Vajna
2016-03-31 14:32 ` Jeff King
2016-03-31 15:02 ` Christian Couder
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=20160331143501.GE19857@collabora.co.uk \
--to=vmiklos@collabora.co.uk \
--cc=git@vger.kernel.org \
--cc=pranit.bauva@gmail.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;
as well as URLs for NNTP newsgroup(s).