From: Jeff King <peff@peff.net>
To: Miklos Vajna <vmiklos@collabora.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Signed-off-by vs Reviewed-by
Date: Thu, 31 Mar 2016 10:32:45 -0400 [thread overview]
Message-ID: <20160331143244.GD31116@sigill.intra.peff.net> (raw)
In-Reply-To: <20160331123507.GC19857@collabora.co.uk>
On Thu, Mar 31, 2016 at 02:35:07PM +0200, Miklos Vajna wrote:
> Hi,
>
> Some projects like LibreOffice don't use Signed-off-by, instead usually
> use Gerrit for code review, and reviewers add a Reviewed-by line when
> they are OK with a patch. In this workflow it's a bit unfortunate that
> adding a Signed-off-by line is just a command-line switch, but adding a
> Reviewed-by line is more complex.
>
> Is there anything in git that could help this situation? I didn't see
> any related config option; I wonder if a patch would be accepted to make
> the "Signed-off-by" line configurable, or there is a better way.
There's git-interpret-trailers, which can do the heavy lifting of adding
it in the right place. But I don't know how you'd want to trigger it; it
would depend on the workflow that people use to add their signoff in the
first place. I don't think there is anything as easy as "git commit
--amend -s", but I'm not all that familiar with the interpret-trailers
code.
-Peff
next prev parent reply other threads:[~2016-03-31 14:32 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
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 [this message]
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=20160331143244.GD31116@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=vmiklos@collabora.co.uk \
/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).