I am using msysgit client, I am able to fetch,push but when I try to pull it shows
git: 'pull' is not a git command. See 'git --help'.
I tried for git --exec-path and it gives C:\git-client/libexec/git-core, this path exists but still I am not able to pull. Any idea?
As stated in comment above:
git pull is (usually) shorthand for doing a fetch then merge.
Check that git fetch works first.
Further later research shows that this may be a bug in a specific version of msysgit, https://code.google.com/p/msysgit/issues/detail?id=249 So try upgrading that also (always prudent advice).
Additionally, a few googles for "git: 'pull' is not a git command" turned up quite a few choices on various fixes, based on which platform you are working on, but most turned out to be a missing path to git-core, so also check those out.
Related
extension: GitHub Pull Requests and Issues
Don't know why its behaving like this, git is installed... still its saying install git
showing:
Activating the Pull Requests and Issues extension failed. Please make sure you have git installed.
Go to setting and search git path
edit the setting.json in there, the last parameter git.path
find the git path with this command in terminal
which git
then reload the VS Code
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 have been struggling with this git problem.
The problem is that when I do a fresh clone from GitHub, git reports that some files has changed although I have not touched them.
Often this happens when I switch branches as well. If I go from an unmodified master to another branch and back to master, it says files has been changed in master.
I have been reading about line endings and tried just about everything in that category, but nothing seems to help.
The repository is https://github.com/seesharper/LightInject is case someone would like to try and see if they have the same problem.
A friend of mine had the exact same problem with the same repository on his Windows 8 machine. Then he tried it on Windows 7 and the problem went away.
Does anybody know of any issues with using git on windows 8.
I have also tried this on another Windows 8 machine and it has the same problem.
I've dealt with this issue in the past - keep in mind that most git installations run on non-windows servers. There's a distinct possibility that what Windows is seeing is actually something where the "filemode" of the file is different than what Linux expects, therefore it sees the file as changed.
Poking around on the internet, there may be a way to fix the filemode issue - but nothing on google is jogging my memory at the moment. I skimmed over this, maybe something in it will help?
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/0EdNev3NNsw
I can't promise the above has a silver bullet for you, but it seems like there's good discussion about how Windows filemode messes up git indexes, sometimes.
I experienced the same issue with Windows 7. This is something I did to resolve (you might try):
git clone git#github.com:seesharper/LightInject.git
cd LightInject
git status
git checkout -f -b mine HEAD~
git status
git checkout master
git status
git branch -D mine
When I try to push new file into Git repository, it doesn't finish, on screen is my workflow:
I tried:
TortoiseGit 1.8.1.0 (git version 1.8.0.msysgit.0 (C:\Program
Files\Git\bin))
Eclipse EGit 2.1.0
Command line
without any success. I read this question, but it's quite old (1.5 year), and do not help (I installed git 1.7.4), and was the same. I new in Git, please tell me what am I doing wrong or how to solve it? What do you suggest as a Git client for Windows 7 (32)? (Best if it will support command line).
Pushing over the Git-protocol is still broken in Git for Windows. So if that's what you're attempting, check if you can push over another protocol instead.
I had this problem today. I pulled and then tried to push to the remote, and it got to 100% writing objects and just stayed there. It didn't request the repo password, nothing.
The solution was related to my .gitconfig file. I had to redo the settings in this file.
I think in mucking around with my git repository (and admittedly learning how git works by breaking it) I had inadvertently removed this file.
I want to create a wiki with gollum and push it to my own git repo, is that possible?
I created a new git repo, install gollum and started it. I got the "edit/Home" page. I added some content, saved...all looked good. Even the "revision history" showed that revisions occurred.
Then I stopped gollum and found there was nothing new in my git repo, I even checked if stuff hadn't been pushed...nothing. I'm not sure how/where it's storing the content that I add when I run it.
Any ideas?
Thanks
Gollum will not sync with a git remote. It will never perform git pull or git push. You must have gollum running on the remote server, or you must manually run git push on machines where you make edits, and git pull on machines who also want to see the wiki. This could be part of a cron job if you're running locally.
It is much easier to have the gollum process running on your web server. See below for more information:
http://www.nomachetejuggling.com/2012/05/15/personal-wiki-using-github-and-gollum-on-os-x/#toc-synchronization-with-github
May be you are checking a wrong repository, the default is for gollum to use or create a git repository at the root of page files. It can be changed with the options --page-file-dir and --base-path (cf gollum --help)