From: Finn Arne Gangstad <finnag@pvv.org>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH] Better errors when trying to merge a submodule
Date: Mon, 10 Dec 2007 13:44:35 +0100 [thread overview]
Message-ID: <20071210124435.GA4788@pvv.org> (raw)
Instead of dying with weird errors when trying to merge submodules from a
supermodule, emit errors that show what the problem is.
Signed-off-by: Finn Arne Gangstad <finnag@pvv.org>
---
If you try to merge a submodule from a supermodule, you get some very
strange error messages. With this patch you get a nice clean error
message indicating that this isn't supported instead.
git-merge-one-file.sh | 7 +++++++
merge-recursive.c | 2 ++
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/git-merge-one-file.sh b/git-merge-one-file.sh
index 1e7727d..7aee342 100755
--- a/git-merge-one-file.sh
+++ b/git-merge-one-file.sh
@@ -82,6 +82,13 @@ case "${1:-.}${2:-.}${3:-.}" in
;;
esac
+ case ",$6,$7," in
+ *,160000,*)
+ echo "ERROR: $4: Not merging submodule."
+ exit 1
+ ;;
+ esac
+
src2=`git-unpack-file $3`
case "$1" in
'')
diff --git a/merge-recursive.c b/merge-recursive.c
index 9a1e2f2..ecae8ea 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -1046,6 +1046,8 @@ static struct merge_file_info merge_file(struct diff_filespec *o,
free(result_buf.ptr);
result.clean = (merge_status == 0);
+ } else if (S_ISGITLINK(a->mode) || S_ISGITLINK(b->mode)) {
+ die("cannot merge submodules!");
} else {
if (!(S_ISLNK(a->mode) || S_ISLNK(b->mode)))
die("cannot merge modes?");
--
1.5.3.7.1149.g591a-dirty
next reply other threads:[~2007-12-10 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 12:44 Finn Arne Gangstad [this message]
2007-12-10 19:22 ` [PATCH] Better errors when trying to merge a submodule Junio C Hamano
2007-12-11 18:11 ` Finn Arne Gangstad
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=20071210124435.GA4788@pvv.org \
--to=finnag@pvv.org \
--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).