From: Calvin Wan <calvinwan@google.com>
To: git@vger.kernel.org
Cc: chooglen@google.com, gitster@pobox.com,
Calvin Wan <calvinwan@google.com>
Subject: [PATCH v2] submodule merge: update conflict error message
Date: Fri, 10 Jun 2022 23:11:52 +0000 [thread overview]
Message-ID: <20220610231152.2594428-1-calvinwan@google.com> (raw)
In-Reply-To: <20220606235449.2890858-1-calvinwan@google.com>
When attempting to do a non-fast-forward merge in a project with
conflicts in the submodules, the merge fails and git prints the
following error:
Failed to merge submodule <submodules>
CONFLICT (submodule):Merge conflict in <submodule>
Automatic merge failed; fix conflicts and then commit the result.
Git is left in a conflicted state, which requires the user to:
1. merge submodules
2. add submodules changes to the superproject
3. merge superproject
These steps are non-obvious for newer submodule users to figure out
based on the error message and neither `git submodule status` nor `git
status` provide any useful pointers.
Update error message to the following when attempting to do a
non-fast-forward merge in a project with conflicts in the submodules.
The error message is based off of what would happen when `merge
--recurse-submodules` is eventually supported
Failed to merge submodule <submodule>
CONFLICT (submodule): Merge conflict in <submodule>
Automatic merge failed; recursive merging with submodules is currently
not supported. To manually complete the merge:
- go to submodule (<submodule>), and merge commit <commit>
- come back to superproject, and `git add <submodule>` to record the above merge
- resolve any other conflicts in the superproject
- commit the resulting index in the superproject
Changes since v1:
- Removed advice to abort merge
- Error message updated to contain more commit/submodule information
Signed-off-by: Calvin Wan <calvinwan@google.com>
---
builtin/merge.c | 23 ++++++++++++++++++++++-
merge-ort.c | 7 ++++++-
merge-recursive.c | 7 ++++++-
merge-recursive.h | 4 ++++
t/t6437-submodule-merge.sh | 5 ++++-
5 files changed, 42 insertions(+), 4 deletions(-)
diff --git a/builtin/merge.c b/builtin/merge.c
index f178f5a3ee..7e2deea7fb 100644
--- a/builtin/merge.c
+++ b/builtin/merge.c
@@ -88,6 +88,8 @@ static const char *sign_commit;
static int autostash;
static int no_verify;
static char *into_name;
+static struct oid_array conflicted_submodule_oids = OID_ARRAY_INIT;
+static struct string_list conflicted_submodule_paths = STRING_LIST_INIT_DUP;
static struct strategy all_strategy[] = {
{ "recursive", NO_TRIVIAL },
@@ -734,6 +736,8 @@ static int try_merge_strategy(const char *strategy, struct commit_list *common,
}
init_merge_options(&o, the_repository);
+ o.conflicted_submodule_oids = &conflicted_submodule_oids;
+ o.conflicted_submodule_paths = &conflicted_submodule_paths;
if (!strcmp(strategy, "subtree"))
o.subtree_shift = "";
@@ -973,8 +977,25 @@ static int suggest_conflicts(void)
strbuf_release(&msgbuf);
fclose(fp);
repo_rerere(the_repository, allow_rerere_auto);
- printf(_("Automatic merge failed; "
+ if (conflicted_submodule_oids.nr > 0) {
+ int i;
+ printf(_("Automatic merge failed; recursive merging with submodules is currently\n"
+ "not supported. To manually complete the merge:\n"));
+ for (i = 0; i < conflicted_submodule_oids.nr; i++) {
+ printf(_(" - go to submodule (%s), and merge commit %s\n"),
+ conflicted_submodule_paths.items[i].string,
+ oid_to_hex(&conflicted_submodule_oids.oid[i]));
+ }
+ printf(_(" - come back to superproject, and `git add"));
+ for (i = 0; i < conflicted_submodule_paths.nr; i++)
+ printf(_(" %s"), conflicted_submodule_paths.items[i].string);
+ printf(_("` to record the above merge \n"
+ " - resolve any other conflicts in the superproject\n"
+ " - commit the resulting index in the superproject\n"));
+ } else {
+ printf(_("Automatic merge failed; "
"fix conflicts and then commit the result.\n"));
+ }
return 1;
}
diff --git a/merge-ort.c b/merge-ort.c
index 0d3f42592f..c86ee11614 100644
--- a/merge-ort.c
+++ b/merge-ort.c
@@ -3866,8 +3866,13 @@ static void process_entry(struct merge_options *opt,
const char *reason = _("content");
if (ci->filemask == 6)
reason = _("add/add");
- if (S_ISGITLINK(merged_file.mode))
+ if (S_ISGITLINK(merged_file.mode)) {
reason = _("submodule");
+ if (opt->conflicted_submodule_oids && opt->conflicted_submodule_paths) {
+ oid_array_append(opt->conflicted_submodule_oids, &merged_file.oid);
+ string_list_append(opt->conflicted_submodule_paths, path);
+ }
+ }
path_msg(opt, path, 0,
_("CONFLICT (%s): Merge conflict in %s"),
reason, path);
diff --git a/merge-recursive.c b/merge-recursive.c
index fd1bbde061..ff7cdbefe9 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -3149,8 +3149,13 @@ static int handle_content_merge(struct merge_file_info *mfi,
}
if (!mfi->clean) {
- if (S_ISGITLINK(mfi->blob.mode))
+ if (S_ISGITLINK(mfi->blob.mode)) {
reason = _("submodule");
+ if (opt->conflicted_submodule_oids && opt->conflicted_submodule_paths) {
+ oid_array_append(opt->conflicted_submodule_oids, &mfi->blob.oid);
+ string_list_append(opt->conflicted_submodule_paths, path);
+ }
+ }
output(opt, 1, _("CONFLICT (%s): Merge conflict in %s"),
reason, path);
if (ci && !df_conflict_remains)
diff --git a/merge-recursive.h b/merge-recursive.h
index b88000e3c2..5d267e7a43 100644
--- a/merge-recursive.h
+++ b/merge-recursive.h
@@ -51,6 +51,10 @@ struct merge_options {
/* internal fields used by the implementation */
struct merge_options_internal *priv;
+
+ /* fields that hold submodule conflict information */
+ struct oid_array *conflicted_submodule_oids;
+ struct string_list *conflicted_submodule_paths;
};
void init_merge_options(struct merge_options *opt, struct repository *repo);
diff --git a/t/t6437-submodule-merge.sh b/t/t6437-submodule-merge.sh
index 178413c22f..5b384dedc1 100755
--- a/t/t6437-submodule-merge.sh
+++ b/t/t6437-submodule-merge.sh
@@ -141,6 +141,7 @@ test_expect_success 'merging should conflict for non fast-forward' '
test_must_fail git merge c 2> actual
fi &&
grep $(cat expect) actual > /dev/null &&
+ test_i18ngrep "go to submodule (sub), and merge commit $(git -C sub rev-parse sub-b)" actual &&
git reset --hard)
'
@@ -167,6 +168,7 @@ test_expect_success 'merging should fail for ambiguous common parent' '
fi &&
grep $(cat expect1) actual > /dev/null &&
grep $(cat expect2) actual > /dev/null &&
+ test_i18ngrep "go to submodule (sub), and merge commit $(git -C sub rev-parse sub-b)" actual &&
git reset --hard)
'
@@ -205,7 +207,8 @@ test_expect_success 'merging should fail for changes that are backwards' '
git commit -a -m "f" &&
git checkout -b test-backward e &&
- test_must_fail git merge f)
+ test_must_fail git merge f >actual &&
+ test_i18ngrep "go to submodule (sub), and merge commit $(git -C sub rev-parse sub-a)" actual)
'
--
2.36.1.476.g0c4daa206d-goog
next prev parent reply other threads:[~2022-06-10 23:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 23:54 [PATCH] submodule merge: update conflict error message Calvin Wan
2022-06-07 0:48 ` Junio C Hamano
2022-06-08 17:19 ` Calvin Wan
2022-06-08 17:34 ` Glen Choo
2022-06-08 18:01 ` Calvin Wan
2022-06-08 19:13 ` Junio C Hamano
2022-06-10 23:11 ` Calvin Wan [this message]
2022-06-11 4:53 ` [PATCH v2] " Elijah Newren
2022-06-11 17:08 ` Philippe Blain
2022-06-12 6:56 ` Elijah Newren
2022-06-13 2:03 ` Calvin Wan
2022-06-12 23:30 ` Junio C Hamano
2022-06-13 1:54 ` Calvin Wan
2022-06-29 22:40 ` [PATCH v3] " Calvin Wan
2022-06-30 2:40 ` Elijah Newren
2022-06-30 19:48 ` Calvin Wan
2022-07-01 4:27 ` Elijah Newren
2022-06-30 20:35 ` Glen Choo
2022-06-30 20:45 ` Glen Choo
2022-06-30 21:08 ` Calvin Wan
2022-07-12 23:19 ` [PATCH v4] " Calvin Wan
2022-07-13 18:11 ` Junio C Hamano
2022-07-17 2:46 ` Elijah Newren
2022-07-15 12:57 ` Johannes Schindelin
2022-07-16 6:22 ` Junio C Hamano
2022-07-17 2:44 ` Elijah Newren
2022-07-18 17:03 ` Calvin Wan
2022-07-18 21:43 ` [PATCH v5] " Calvin Wan
2022-07-19 6:39 ` Junio C Hamano
2022-07-19 19:30 ` Calvin Wan
2022-07-19 20:16 ` Junio C Hamano
2022-07-19 7:13 ` Junio C Hamano
2022-07-19 19:07 ` Calvin Wan
2022-07-19 20:30 ` Junio C Hamano
2022-07-25 6:05 ` Ævar Arnfjörð Bjarmason
2022-07-25 12:11 ` Ævar Arnfjörð Bjarmason
2022-07-25 22:03 ` Calvin Wan
2022-07-25 12:31 ` Ævar Arnfjörð Bjarmason
2022-07-25 21:27 ` Calvin Wan
2022-07-26 21:00 ` [PATCH v6] " Calvin Wan
2022-07-27 1:13 ` Elijah Newren
2022-07-27 22:00 ` Calvin Wan
2022-07-28 0:41 ` Elijah Newren
2022-07-28 19:06 ` Calvin Wan
2022-07-27 9:20 ` Ævar Arnfjörð Bjarmason
2022-07-28 21:12 ` [PATCH v7] " Calvin Wan
2022-07-28 23:22 ` Ævar Arnfjörð Bjarmason
2022-07-29 0:24 ` Elijah Newren
2022-08-01 22:24 ` Calvin Wan
2022-08-01 12:06 ` Ævar Arnfjörð Bjarmason
2022-08-02 0:50 ` Junio C Hamano
2022-08-02 21:03 ` Calvin Wan
2022-08-02 21:11 ` Junio C Hamano
2022-08-02 21:55 ` Calvin Wan
2022-08-02 22:22 ` Junio C Hamano
2022-08-04 19:51 ` [PATCH v8] " Calvin Wan
2022-08-16 15:58 ` Junio C Hamano
2022-08-16 18:58 ` Junio C Hamano
2022-08-16 19:34 ` Calvin Wan
2022-08-16 19:39 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220610231152.2594428-1-calvinwan@google.com \
--to=calvinwan@google.com \
--cc=chooglen@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).