From: Zaoshi <kabazaoshi@gmail.com>
To: git@vger.kernel.org
Subject: git mergetool does not work since 2.29.0
Date: Wed, 28 Oct 2020 09:25:25 +0200 [thread overview]
Message-ID: <a284dc99-7da3-a313-6d9b-1dd40cbc5b22@gmail.com> (raw)
Hello,
I have tried using 'git bugreport' but could not figure out how to edit
text in the console and send report, so I'm just reusing that form in
this email. Let me know if any other information is needed.
What did you do before the bug happened?
Ran the following commands:
git checkout mybranch
git merge master
git mergetool
What did you expect to happen?
I expected git to open my configured mergetool
What happened instead?
It fails with message "merge of myfile.cs failed"
What's different between what you expected and what actually happened?
Merge does not work.
Anything else you want to add:
This issue started to happen since git version 2.29.0. Earlier versions
work as expected.
.gitconfig:
[core]
editor = \"C:\\Microsoft VS Code\\Code.exe\" --wait
[user]
name = myname
email = myemail
[fetch]
prune = true
[pull]
rebase = true
[diff]
tool = bc4
[merge]
tool = bc4
[difftool "bc4"]
cmd = \"c:\\Program Files\\Beyond Compare 4\\bcomp.exe\" $LOCAL $REMOTE
trustExitCode = true
[mergetool "bc4"]
cmd = \"c:\\Program Files\\Beyond Compare 4\\bcomp.exe\" $LOCAL
$REMOTE $BASE $MERGED
trustExitCode = true
[System Info]
git version:
git version 2.29.1.windows.1
cpu: x86_64
built from commit: e6d53c456169235fe72602e2b4d985934fa9ad23
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
uname: Windows 10.0 19041
compiler info: gnuc: 10.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
Regards,
Z
next reply other threads:[~2020-10-28 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 7:25 Zaoshi [this message]
2020-12-01 20:58 ` git mergetool does not work since 2.29.0 Johannes Schindelin
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=a284dc99-7da3-a313-6d9b-1dd40cbc5b22@gmail.com \
--to=kabazaoshi@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).