Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

git mergetool should be considered correctly configured even there's no path. #6438

Closed
SetoKaiba opened this issue Apr 5, 2019 · 0 comments
Closed

git mergetool should be considered correctly configured even there's no path. #6438

SetoKaiba opened this issue Apr 5, 2019 · 0 comments
Labels
type: bug 🐛
Milestone
3.1.0

Comments

@SetoKaiba
Copy link
Contributor

Current behaviour

git mergetool is considered incorrectly configured when there's no path.

Expected behaviour

git mergetool should be considered correctly configured even there's no path.

Steps to reproduce

just specified cmd only

Screenshots

image

Environment

  • Git Extensions 3.0.2.5232
  • Build 23b6f51
  • Git 2.21.0.windows.1
  • Microsoft Windows NT 10.0.17134.0
  • .NET Framework 4.7.3362.0
  • DPI 96dpi (no scaling)
@SetoKaiba SetoKaiba mentioned this issue Apr 5, 2019
Merged
RussKie added a commit that referenced this issue Apr 6, 2019
@RussKie
Merge pull request #6439 from SetoKaiba/fix_6438
90ea250 
fix #6438
@RussKie RussKie added this to the 3.1.0 milestone Apr 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug 🐛
Projects
None yet
Milestone
3.1.0
Development

No branches or pull requests
2 participants
@SetoKaiba @RussKie