From: Elijah Newren <newren@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>
Subject: [PATCH 0/6] Miscellaneous merge fixes
Date: Sat, 9 Apr 2016 23:13:34 -0700 [thread overview]
Message-ID: <1460268820-8308-1-git-send-email-newren@gmail.com> (raw)
This series has four independent miscellaneous fixes, three split out
from my RFC series at $gmane/291007 and one new fix. These four fixes
have no dependencies on each other, so I can trivially split them into
four submissions if preferred. I only batched them because I want my
index-only merge series to be able to simultaneously depend on three
of them.
The first patch is a very minor code cleanup, which has already been
reviewed by Junio.
The second patch is also a minor code cleanup.
The third and fourth patches test and fix a bug with octopus merges.
Since last submitting these patches with my RFC series, I discovered
our documentation used to explicitly state the expectation I enforced
with these patches. I added a note about that in the commit message.
The fifth and sixth patches test and fix a bug with trivial merges;
these patches are new since my RFC series.
Elijah Newren (6):
Remove duplicate code
Avoid checking working copy when creating a virtual merge base
Add merge testcases for when index doesn't match HEAD
merge-octopus: Abort if index does not match HEAD
Add a testcase demonstrating a bug with trivial merges
builtin/merge.c: Fix a bug with trivial merges
builtin/merge.c | 8 ++
git-merge-octopus.sh | 6 ++
merge-recursive.c | 8 +-
t/t6044-merge-unrelated-index-changes.sh | 153 +++++++++++++++++++++++++++++++
t/t7605-merge-resolve.sh | 6 +-
5 files changed, 175 insertions(+), 6 deletions(-)
create mode 100755 t/t6044-merge-unrelated-index-changes.sh
--
2.8.0.21.g229f62a
next reply other threads:[~2016-04-10 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 6:13 Elijah Newren [this message]
2016-04-10 6:13 ` [PATCH 1/6] Remove duplicate code Elijah Newren
2016-04-10 6:13 ` [PATCH 2/6] Avoid checking working copy when creating a virtual merge base Elijah Newren
2016-04-13 1:28 ` Junio C Hamano
2016-04-10 6:13 ` [PATCH 3/6] Add merge testcases for when index doesn't match HEAD Elijah Newren
2016-04-10 6:13 ` [PATCH 4/6] merge-octopus: Abort if index does not " Elijah Newren
2016-04-10 6:13 ` [PATCH 5/6] Add a testcase demonstrating a bug with trivial merges Elijah Newren
2016-04-10 6:13 ` [PATCH 6/6] builtin/merge.c: Fix " Elijah Newren
2016-04-13 1:23 ` [PATCH 0/6] Miscellaneous merge fixes Junio C Hamano
2016-04-15 21:14 ` Elijah Newren
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=1460268820-8308-1-git-send-email-newren@gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
/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).