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.

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

git command error on GitLens 9.7.0 (unknown '-M' option) #736

Closed
zedaav opened this issue May 6, 2019 · 14 comments

Comments

Projects
None yet
10 participants
@zedaav
Copy link

commented May 6, 2019

  • GitLens Version: 9.7.0
  • VSCode Version: 1.33.1
  • OS Version: Ubuntu 18.04.2 LTS
  • git version: 2.17.1

I'm just getting this behavior from this morning, once GitLens got updated to 9.7.0
I tried with different workspaces, and I'm still getting the error.
When I install back 9.6.3 version, the behavior disappears.

Steps to Reproduce:

  1. Just open a file in VS Code, and try to display any Gitlens view (Repository, File History...)
  2. I get a notification with the following error:

Command failed: /usr/bin/git -c core.quotepath=false -c color.ui=false -c color.status=false status --porcelain=v2 -M -- Makefile
error: unknown switch `M'
usage: git status [] [--] ...

-v, --verbose         be verbose
-s, --short           show status concisely
-b, --branch          show branch information
--show-stash          show stash information
--ahead-behind        compute full ahead/behind values
--porcelain[=<version>]
                      machine-readable output
--long                show status in long format (default)
-z, --null            terminate entries with NUL
-u, --untracked-files[=<mode>]
                      show untracked files, optional modes: all, normal, no. (Default: all)
--ignored[=<mode>]    show ignored files, optional modes: traditional, matching, no. (Default: traditional)
--ignore-submodules[=<when>]
                      ignore changes to submodules, optional when: all, dirty, untracked. (Default: all)
--column[=<style>]    list untracked files in columns

Output logs:
output-gitlens.txt
output-gitlens-git.txt

@light8lee

This comment has been minimized.

Copy link

commented May 6, 2019

Same error with you when I upgrated GitLens to 9.7.0

@dalisoft

This comment has been minimized.

Copy link

commented May 6, 2019

Same error

@shx996

This comment has been minimized.

Copy link

commented May 6, 2019

Same error! @eamodio

@yyonggithub

This comment has been minimized.

Copy link

commented May 6, 2019

Same error

@AlexanderVasiliev

This comment has been minimized.

Copy link

commented May 6, 2019

update git to last version helped

@eamodio

This comment has been minimized.

Copy link
Owner

commented May 6, 2019

Damn, sorry all. It looks like that parameter is only support in Git 2.18 or later. I'll push out a new release shortly to fix this.

@bracco23

This comment has been minimized.

Copy link

commented May 6, 2019

git version 2.17.1.windows.2 here, seeing the same error.

@eamodio eamodio closed this in 46f7d6c May 6, 2019

@eamodio

This comment has been minimized.

Copy link
Owner

commented May 6, 2019

9.7.1 will be in the marketplace very shortly -- sorry for the issue!

@dalisoft

This comment has been minimized.

Copy link

commented May 6, 2019

On macOS helped upgrade git with Homebrew and echo 'export PATH="/usr/local/git/bin:/usr/local/sbin:$PATH"' >> ~/.bash_profile then restart VSCode.
@eamodio thanks for fast reply and fix

@BraveHead

This comment has been minimized.

Copy link

commented May 6, 2019

same error

@zedaav

This comment has been minimized.

Copy link
Author

commented May 6, 2019

Just installed 9.7.1
Fix confirmed!
Thanks @eamodio 👍

@eamodio

This comment has been minimized.

Copy link
Owner

commented May 6, 2019

@BraveHead the same with 9.7.1?

@BraveHead

This comment has been minimized.

Copy link

commented May 6, 2019

@BraveHead the same with 9.7.1?
Update to 9.7.1 is fine.

@Cheng-Ya

This comment has been minimized.

Copy link

commented May 6, 2019

same error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.