From: Miklos Vajna <vmiklos@collabora.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: Pranit Bauva <pranit.bauva@gmail.com>,
Git List <git@vger.kernel.org>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: Signed-off-by vs Reviewed-by
Date: Fri, 1 Apr 2016 16:10:36 +0200 [thread overview]
Message-ID: <20160401141036.GG800@collabora.co.uk> (raw)
In-Reply-To: <xmqqtwjmpq6b.fsf@gitster.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
Hi,
On Thu, Mar 31, 2016 at 09:28:44AM -0700, Junio C Hamano <gitster@pobox.com> wrote:
> The internal "parse the existing trailer block and manipulate it by
> adding, conditionally adding, replacing and deleting it" logic was
> done as an experimental "interpret-trailers" program, but polishing
> it (both its design and implementation) and integrating it to the
> front-line programs (e.g. "git commit") hasn't been done.
I had a look at interpret-trailers, and one use-case I miss is: being
able to define a trailer type, but only add it when asked explicitly.
Example:
----
$ git config trailer.review.key "Reviewed-by: "
$ git config trailer.review.command 'echo "$(git config user.name) <$(git config user.email)>"'
$ echo foo|git interpret-trailers
foo
Reviewed-by: A U Thor <author@example.com>
$ echo foo|git interpret-trailers --trailer review
foo
Reviewed-by: A U Thor <author@example.com>
----
I can imagine e.g. a new configuration vaulue named
trailer.<token>.ifMissing explicit, and when that's set, the trailer
would be only added if it's spelled out explicitly using '--trailer
<token>'.
Does this sound like a good idea, or did I miss some way how this is
already possible? :-)
> As to the last step of "integration", we cannot use short-and-sweet
> single letter options like '-s' (for sign-off) for each and every
> custom trailer different projects use for their own purpose (as
> there are only 26 of the lowercase ASCII alphabet letters), so the
> most general syntax for the option has to become "--trailer <arg>"
> or some variation of it, and at that point "-s" would look like a
> short-hand for "--trailer signed-off-by".
Hmm, I think the above has to be implemented first, otherwise it'll be
hard to make "-s" an alias of "--trailer signed-off-by". (I mean having
git understand what "signed-off-by" is, still adding it conditionally.)
Regards,
Miklos
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-04-01 14:10 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 [this message]
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=20160401141036.GG800@collabora.co.uk \
--to=vmiklos@collabora.co.uk \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).