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 11:21:24 -0700 [thread overview]
Message-ID: <1472581284.5512.117.camel@perches.com> (raw)
In-Reply-To: <xmqqshtm3yur.fsf@gitster.mtv.corp.google.com>
On Tue, 2016-08-30 at 11:17 -0700, Junio C Hamano wrote:
> Joe Perches <joe@perches.com> writes:
>
> >
> > On Tue, 2016-08-30 at 10:41 -0700, Joe Perches wrote:
> > >
> > > Maybe something like traces or chains.
> > Or "taggers" or "tagged-bys"
> I am afraid that you are way too late; the ship has already sailed a
> few years ago, if not earlier, I think.
What's the ship's name? Is it footers or trailers?
next prev parent reply other threads:[~2016-08-30 18:21 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
2016-08-30 17:49 ` Joe Perches
2016-08-30 18:17 ` Junio C Hamano
2016-08-30 18:21 ` Joe Perches [this message]
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=1472581284.5512.117.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.