git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Pat Thoyts" <patthoyts@gmail.com>, "René Scharfe" <l.s.r@web.de>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] git-gui: pass the branch name to git merge
Date: Wed, 23 Nov 2016 23:36:36 +0100	[thread overview]
Message-ID: <e61cc267-a59b-3be1-29db-c49d56f521f7@kdbg.org> (raw)
In-Reply-To: <xmqq4m2ym06p.fsf@gitster.mtv.corp.google.com>

Am 23.11.2016 um 21:05 schrieb Junio C Hamano:
> Johannes Sixt <j6t@kdbg.org> writes:
>> Am 22.11.2016 um 21:40 schrieb Johannes Sixt:
>>> Am 22.11.2016 um 20:16 schrieb Junio C Hamano:
>>>> Can't this be handled on the "git merge FETCH_HEAD" codepath
>>>> instead?
>>>
>>> Absolutely. Any takers? ;)
>>
>> I attempted to fix git merge FETCH_HEAD, but I do not see a trivial
>> solution.
>>
>> But on second thought, we have an excuse to pick my proposed git-gui
>> change anyway: Without that change and a fix in git-merge only, there
>> is still a regression for all users who use the latest git-gui but
>> some git version between 2.5.0 and the fixed git-merge...
> 
> I'll leave it up to Pat, as I do not read tcl very well ;-)

Sure!

In the mean time, here is my attempt to fix git merge FETCH_HEAD.
I would feel better if this were just taken as a starter for a
real fix by someone who is familiar with the area.

---- 8< ----
[PATCH] merge FETCH_HEAD: keep track of the branch names

'git merge FETCH_HEAD' is treated differently from 'git merge topic'
because FETCH_HEAD is not just a regular ref name, but contains the
names of the branches being merged. However, 'git merge' does not
store the names as the "remote description" of the merge parent
structure that is associated with merged commits, like an ordinary
'git merge topic' call does for the command line arguments.
A consequence is that conflict markers are not marked up with the
branch name, but with a raw object name. Parse off the branch names
from the FETCH_HEAD file and store them with the merged commits.

Signed-off-by: Johannes Sixt <j6t@kdbg.org>
---
 builtin/merge.c | 8 ++++++++
 commit.c        | 1 +
 2 files changed, 9 insertions(+)

diff --git a/builtin/merge.c b/builtin/merge.c
index b65eeaa87d..328517b091 100644
--- a/builtin/merge.c
+++ b/builtin/merge.c
@@ -1051,9 +1051,17 @@ static void handle_fetch_head(struct commit_list **remotes, struct strbuf *merge
 			continue; /* not-for-merge */
 		else {
 			char saved = merge_names->buf[pos + 40];
+			char eol = ptr ? *ptr : '\0';
 			merge_names->buf[pos + 40] = '\0';
+			if (ptr)
+				*ptr = '\0';
 			commit = get_merge_parent(merge_names->buf + pos);
+			set_merge_remote_desc(commit,
+					merge_names->buf + pos + 40 + 2,
+					merge_remote_util(commit)->obj);
 			merge_names->buf[pos + 40] = saved;
+			if (ptr)
+				*ptr = eol;
 		}
 		if (!commit) {
 			if (ptr)
diff --git a/commit.c b/commit.c
index 856fd4aeef..7ac2ce6518 100644
--- a/commit.c
+++ b/commit.c
@@ -1582,6 +1582,7 @@ void set_merge_remote_desc(struct commit *commit,
 	struct merge_remote_desc *desc;
 	FLEX_ALLOC_STR(desc, name, name);
 	desc->obj = obj;
+	free(commit->util);
 	commit->util = desc;
 }
 
-- 
2.11.0.rc1.52.g65ffb51


      reply	other threads:[~2016-11-23 22:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 17:52 [PATCH] git-gui: pass the branch name to git merge Johannes Sixt
2016-11-22 19:16 ` Junio C Hamano
2016-11-22 20:40   ` Johannes Sixt
2016-11-23 19:23     ` Johannes Sixt
2016-11-23 20:05       ` Junio C Hamano
2016-11-23 22:36         ` Johannes Sixt [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=e61cc267-a59b-3be1-29db-c49d56f521f7@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=l.s.r@web.de \
    --cc=patthoyts@gmail.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).