From: Willy Tarreau <w@1wt.eu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
Christian Couder <christian.couder@gmail.com>,
Brandon Casey <drafnel@gmail.com>
Subject: Re: [PATCH] sequencer.c: fix detection of duplicate s-o-b
Date: Wed, 6 Apr 2016 18:37:26 +0200 [thread overview]
Message-ID: <20160406163726.GG28596@1wt.eu> (raw)
In-Reply-To: <xmqqr3eizsxu.fsf@gitster.mtv.corp.google.com>
On Wed, Apr 06, 2016 at 07:57:01AM -0700, Junio C Hamano wrote:
> This seems to have been lost, perhaps because the top part that was
> quite long didn't look like a patch submission message or something.
Don't worry, we all know it's the submitter's responsibility to retransmit,
I apply the same principle :-)
> Git 1.7.12 is a quite ancient release and I wouldn't be surprised if
> we made the behaviour change during the period leading to v2.6 on
> purpose, but nothing immediately comes to mind. Christian (as the
> advocate for the trailer machinery) and Brandon ("git shortlog
> sequencer.c" suggests you), can you take a look?
FWIW it wad changed in 1.8.3 by commit bab4d10 ("sequencer.c: teach
append_signoff how to detect duplicate s-o-b").
The change made a lot of sense but it didn't assume that this practice
was common. And indeed I think this practice only happens in maintenance
branches where people have to make a lot of adaptations to existing
patches that they're cherry-picking. We do that a lot in stable kernels
to keep track of what we may need to revisit if we break something.
Thanks!
Willy
next prev parent reply other threads:[~2016-04-06 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 13:08 [PATCH] sequencer.c: fix detection of duplicate s-o-b Willy Tarreau
2016-04-06 14:57 ` Junio C Hamano
2016-04-06 16:37 ` Willy Tarreau [this message]
2016-04-07 20:06 ` Christian Couder
2016-04-07 20:16 ` Willy Tarreau
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=20160406163726.GG28596@1wt.eu \
--to=w@1wt.eu \
--cc=christian.couder@gmail.com \
--cc=drafnel@gmail.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 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).