From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Toon Claes <toon@iotcl.com>
Cc: "Jeff King" <peff@peff.net>, "Junio C Hamano" <gitster@pobox.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
git@vger.kernel.org, "Zeger-Jan van de Weg" <git@zjvandeweg.nl>
Subject: Re: [PATCH 1/1] commit: add support to provide --coauthor
Date: Thu, 10 Oct 2019 23:07:17 +0000 [thread overview]
Message-ID: <20191010230716.rylvyiyqu4gv4zcc@camp.crustytoothpaste.net> (raw)
In-Reply-To: <87sgo1q92k.fsf@iotcl.com>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On 2019-10-10 at 08:49:23, Toon Claes wrote:
> Jeff King <peff@peff.net> writes:
>
> > Yeah, I'd agree that we should start first with a generic trailer line.
>
> IIUC you are suggesting something like this?
>
> git commit --trailer="Co-authored-by: <coauthor>"
>
> I really want to consider this, but I do not understand how that improves
> the user experience compared to adding that trailer manually when typing the
> commit message in your $EDITOR?
The --trailer option to git interpret-trailers knows how to interpret
configuration options and expand them. For example, you could
abbreviate "Co-authored-by" as "cab", and if you used that alias, you
could write "git commit --trailer='cab=peff'" and then have your command
look up "peff" and find the proper identification either from your repo
or from your Git hosting solution of choice (or wherever).
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2019-10-10 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 7:49 [PATCH 1/1] commit: add support to provide --coauthor Toon Claes
2019-10-08 8:35 ` Denton Liu
2019-10-08 10:11 ` Phillip Wood
2019-10-08 12:04 ` Phillip Wood
2019-10-09 1:40 ` SZEDER Gábor
2019-10-09 2:19 ` Junio C Hamano
2019-10-09 11:20 ` brian m. carlson
2019-10-09 11:37 ` Junio C Hamano
2019-10-09 20:31 ` Jeff King
2019-10-10 8:49 ` Toon Claes
2019-10-10 16:37 ` Jeff King
2019-10-11 4:09 ` Junio C Hamano
2019-10-10 23:07 ` brian m. carlson [this message]
2019-10-10 11:49 ` Johannes Schindelin
2019-10-10 17:00 ` Denton Liu
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=20191010230716.rylvyiyqu4gv4zcc@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=git@zjvandeweg.nl \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=szeder.dev@gmail.com \
--cc=toon@iotcl.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 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.