From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t5516: fix mismerge in 'next'
Date: Mon, 22 Apr 2019 15:25:38 +0900 [thread overview]
Message-ID: <xmqq4l6q8skd.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190422044812.GA28493@sigill.intra.peff.net> (Jeff King's message of "Mon, 22 Apr 2019 00:48:12 -0400")
Jeff King <peff@peff.net> writes:
> The merge of jk/fetch-reachability-error-fix conflicts with
> jt/test-protocol-version, but the conflict resolution done by
> b4ce8375c018 has a typo (looks like an editor mistake):
> ...
Indeed it was. Thanks for spotting.
> The same problem is present in the merges to pu, which is not surprising
> since the 'next' merge was probably just resolved by rerere.
Yup, here is what I did:
$ git checkout b4ce8375c018
$ git am jk-t5516-fix.patch
$ CG=$(git describe)
$ git reset --hard b4ce8375c018^
$ git merge jk/fetch-reachability-error-fix
$ git rerere forget t/t5516-fetch-push.sh
$ git diff $CG ;# shows the typo
$ git checkout $CG t/t5516-fetch-push.sh
# I should learn to use 'git restore' one of these days.
$ git diff ;# shows --cc
$ git rerere
$ git reset --hard
$ git merge jk/fetch-reachability-error-fix
$ git diff $CG ;# shows no difference
That should teach rerere about the right resolution. And to carry
the fix in 'next':
$ git checkout next
$ git am -s3 jk-t5516-fix.patch
Thanks.
prev parent reply other threads:[~2019-04-22 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 4:48 [PATCH] t5516: fix mismerge in 'next' Jeff King
2019-04-22 6:25 ` Junio C Hamano [this message]
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=xmqq4l6q8skd.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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 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).