From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Taylor Blau <me@ttaylorr.com>, David Caro <dcaro@wikimedia.org>,
git@vger.kernel.org
Subject: Re: Skipping adding Signed-off-by even if it's not the last on git commit
Date: Fri, 09 Dec 2022 13:03:44 +0900 [thread overview]
Message-ID: <xmqqcz8t1avz.fsf@gitster.g> (raw)
In-Reply-To: <Y5KSfsxLO7com2f9@coredump.intra.peff.net> (Jeff King's message of "Thu, 8 Dec 2022 20:42:22 -0500")
Jeff King <peff@peff.net> writes:
>> > git config trailer.sign.key Signed-off-by
>> > git config trailer.sign.cmd \
>> > 'git var GIT_COMMITTER_IDENT | sed "s/>.*/>/";:'
>> > git commit --trailer=sign
>> >
>> > which is only a little more typing than --signoff, but it's not very
>> > ergonomic.
>>
>> It does not look _too_ bad, though.
>
> What I don't like about it is:
>
> - the external cmd is complicated and slow. It would be nice if you
> could just set trailer.sign.ident=true or something, and it would
> use your ident by default if no value is given (and maybe even do
> completion similar to "commit --author" if a value is given).
Ah, "trailer.sign.value" to use the same value does not exist, and
the closest kludge we can use is the .cmd thing? Then it is a shame
but it should be easy to correct?
> - you have to know to be clever enough to define and use
> --trailer=sign. If --signoff didn't exist, that's not too big a
> stretch. But since it does, everyone will naturally reach for it
> first.
We could reimplement --signoff to actually take attention to the
"trailer.sign.*" thing, if we wanted to, and that makes it very easy
to explain, I guess.
next prev parent reply other threads:[~2022-12-09 4:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 17:06 Skipping adding Signed-off-by even if it's not the last on git commit David Caro
2022-12-07 1:50 ` Taylor Blau
2022-12-07 4:11 ` Junio C Hamano
2022-12-07 8:40 ` David Caro
2022-12-07 22:13 ` Taylor Blau
2022-12-07 23:04 ` Junio C Hamano
2022-12-08 7:27 ` Jeff King
2022-12-09 1:23 ` Junio C Hamano
2022-12-09 1:42 ` Jeff King
2022-12-09 4:03 ` Junio C Hamano [this message]
2022-12-09 20:39 ` Jeff King
2022-12-07 4:31 ` Ævar Arnfjörð Bjarmason
2022-12-07 4:57 ` Junio C Hamano
2022-12-07 15:00 ` Konstantin Ryabitsev
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=xmqqcz8t1avz.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dcaro@wikimedia.org \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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.