Installing git ver 2.15.0 and 2.14.2 on Windows 10 freezes before finishing the install. The only way to close the install window is to kill the process or restart my machine.
After restarting, git Bash will open but it opens in a frozen state. If I try to run commands from an Admin Windows command prompt, some of them work but git push and git stash also just hang there, and do nothing.
I've search around and have found that others have problems with git on Windows 10 but haven't found any solutions.
Any suggestions or is there any type of error logging with git?
Thanks
Related
git status, git branch and git log for example are running slow when I issue the commands from a regular privilege powershell.
However, if I run the powershell prompt with admin privileges and I run the above commands, they execute quickly without any issues.
Any thoughts please?
Adding git.exe as a process exclusion didn't work for me, but adding C:\Program Files\Git\* (also as a process exclusion) solved my issues.
After that, git pull and fetch went from 100 secs to 3 secs in Git Bash, PS and SourceTree.
When I type git add --patch on my Windows 10 machine in the terminal, I get the error:
git: 'add--interactive' is not a git command. See 'git --help'.
I've googled to no avail, all other problems seem to be people running into this issue using other software or on Linux. Any tips?
This thread (for Git on Linux) mentioned the lack of a git-perl package.
But that should not be the case on Windows.
For testing, download PortableGit-2.17.0-64-bit.7z.exe and uncompress its content anywhere you want.
Then setup a simplified PATH:
set G=c:\path\to\latest\git
set PATH=%G%\bin;%G%\usr\bin;%G%\mingw64\bin
set PATH=%PATH%;C:\windows\system32;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\
In that CMD session, try again your git add -p command.
I'm trying to use Git Extensions on a new Windows 7 machine. I have done that many times before but never hit this particular issue.
Git Bash is working, I successfully cloned a repository.
But going to Git Extensions, opening the repo, and doing a pull gives me the following error message:
"C:\Program Files (x86)\Git\bin\git.exe" pull --progress "origin"
error: cannot spawn git: Function not implemented
Done
Press Enter or Esc to close console...
My setup is very ordinary. The Git Extensions startup checks all pass. (This is similar but not the same problem as the common invalid path issue.)
Do you have any idea what causes this problem?
The new releases, Git for Windows 2.16.1(3) and Git for Windows 2.16.1(4), fix this regression:
2.16.1(3) Bug Fixes
When http.sslBackend is not configured (e.g. in portable Git or MinGit), fetch/push operations no longer crash.
On Windows 7 and older, Git for Windows v2.16.1(2) was no longer able to spawn any processes (e.g. during fetch/clone). This regression has been fixed.
The Perl upgrade in v2.16.1(2) broke git send-email; This has been fixed by updating the Net-SSLeay Perl module.
The mentioned regression in the second bullet point is exactly the error this question is about.
Unfortunately, there was one missing issue about spawning processes which was then fixed in the subsequent fourth release:
2.16.1(4) Bug Fixes
When called from TortoiseGit, git.exe can now spawn processes again.
Note that the download on https://git-scm.com/download/win might not have been update yet, so you need to download it from gitforwindows.org or directly from the release page on GitHub.
Afterwards, you can verify that you indeed running the new version using git --version which should report git version 2.16.1.windows.4.
Per Philippe and Jake - bug is filed against GIT 2.16.2, and workaround is to go back to prior version.
https://github.com/git-for-windows/git/releases/tag/v2.16.1.windows.1
Running an update on my machine to Git for Windows v2.21.0- just a slightly updated version fixed the issue with my Windows 7 installation at work.
https://github.com/git-for-windows/git/releases/download/v2.21.0.windows.1/Git-2.21.0-32-bit.exe
I've been trying to resolve a problem where I'm unable to clone --recursive from github. I went through the instructions. I finished all of the commands, and after running the command:
git config --global credential.helper osxkeychain
, the terminal is just hung up.
When I attempt to quit it, it tells me git is still running. Ctrl-C reveals [Process completed] but still no command prompt.
I've tried to delete the com.apple.Terminal.plist file, but that just deletes my preferences. I've tried rebooting as well.
I'm using Mac OS X 10.8.2
I was working on a git repo, and because it seemed like my machine was slowing down (and had about 15 days of uptime), I decided to restart. I immediately opened iTerm2, and went back to work, but git is not responding to any commands. I'll paste the output of my console, so you can see me trying things, giving up after 2 minutes of getting no response, checking the path to git to make sure it's installed, etc.
Nick-Coxs-Macbook-Pro:codealong macbookpro$ git status
^C
Nick-Coxs-Macbook-Pro:codealong macbookpro$ git gc
^C
Nick-Coxs-Macbook-Pro:codealong macbookpro$ git stash
^C
Nick-Coxs-Macbook-Pro:codealong macbookpro$ git reset --hard HEAD^
^C
Nick-Coxs-Macbook-Pro:codealong macbookpro$ which git
/usr/bin/git
Nick-Coxs-Macbook-Pro:codealong macbookpro$ git status
You can see with the ^C that I've just pressed ctrl + C to get out of it.
A few things I'm sure of:
I'm definitely connected to the internet. (Proof: I posted this question.) Even if I weren't, git should still work locally.
This is definitely a git repo. Even if it weren't, git would say it wasn't. It wouldn't just hang.
I've also tried this in plain Terminal (as opposed to iTerm2). No difference.
I'm on OS X Lion 10.7.4.
UPDATE: I've repaired permissions on my machine with Disk Utility, and this is still happening on ALL git repos on my machine.
UPDATE2: Here is the output of my console while git is doing nothing.
10/20/12 7:23:48.364 PM com.apple.launchd.peruser.501: (com.Eltima.SyncMateServer[543]) posix_spawn("/Library/Application Support/EltimaSyncMate/SyncMateServer.app/Contents/MacOS/SyncMateServer", ...): No such file or directory
10/20/12 7:23:48.365 PM com.apple.launchd.peruser.501: (com.Eltima.SyncMateServer[543]) Exited with code: 1
10/20/12 7:23:48.365 PM com.apple.launchd.peruser.501: (com.Eltima.SyncMateServer) Throttling respawn: Will start in 10 seconds
That doesn't mean anything to me. Anyone?
UPDATE3: I don't know why I didn't check this earlier, but I am able to use GitX as a GUI for git, so it's not that git doesn't work per se, but CLI doesn't work.
UPDATE 4: I restarted in Safe Mode, but terminal still treats git the same way.
I'm still not quite sure why this was happening, but I was able to fix it. I uninstalled git with a simple rm /usr/local/bin/git (which would, of course, change based on the location of the installation), then I reinstalled it with this installer (note that it worked for 10.7 Lion, even though it is ostensibly the Snow Leopard binary) because I found out that git was just recently updated to 1.8.