From: Joe Perches <joe@perches.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git am and duplicate signatures
Date: Tue, 30 Aug 2016 10:41:19 -0700 [thread overview]
Message-ID: <1472578879.5512.111.camel@perches.com> (raw)
In-Reply-To: <xmqq8tve5fet.fsf@gitster.mtv.corp.google.com>
On Tue, 2016-08-30 at 10:34 -0700, Junio C Hamano wrote:
> Joe Perches <joe@perches.com> writes:
> > On Tue, 2016-08-30 at 09:54 -0700, Junio C Hamano wrote:
> > >
> > > Support for more generic footers was supposed to come when the
> > > "interpret-trailers" topic started, but the author of the topic
> > > seems to have lost interest before the mechanism has become ready to
> > > be integrated in the workflow commands like "am", "commit", "rebase"
> > > etc., which is unfortunate.
> > I think adding at least an option to git send-email
> > allowing auto-cc's for all
> > "<foo>-by: [name] <address>"
> > lines in the commit log would be useful.
> >
> > Today, only "Signed-off-by" and "CC" lines are
> > added to cc's.
> >
> > I've always called these lines "-by:" lines
> > "signatures", but perhaps there's a better name.
> I think we casually call them footers (as they are counter-part to
> "headers"), or trailers.
I think they are neither footers, which would relate
more to the email headers, nor trailers.
Maybe something like traces or chains.
btw: I submitted this awhile ago
http://www.spinics.net/lists/git/msg162269.html
next prev parent reply other threads:[~2016-08-30 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 16:12 git am and duplicate signatures Joe Perches
2016-08-30 16:54 ` Junio C Hamano
2016-08-30 17:07 ` Joe Perches
2016-08-30 17:37 ` Junio C Hamano
2016-08-30 17:26 ` Joe Perches
2016-08-30 17:34 ` Junio C Hamano
2016-08-30 17:41 ` Joe Perches [this message]
2016-08-30 17:49 ` Joe Perches
2016-08-30 18:17 ` Junio C Hamano
2016-08-30 18:21 ` Joe Perches
2016-08-30 19:00 ` Junio C Hamano
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=1472578879.5512.111.camel@perches.com \
--to=joe@perches.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.