msysgit

How do I write a batch file which opens the GitBash shell and runs a command in the shell?

馋奶兔 提交于 2019-11-27 06:44:13
I'm on Windows 7 trying to use a batch file to open the GitBash shell and make a git call. This is the contents of my batch file: REM Open GitBash C:\Windows\SysWOW64\cmd.exe /c ""C:\Program Files (x86)\Git\bin\sh.exe" --login -i" REM retrieve archive git archive master | tar -x -C %~1 REM quit GitBash exit I noticed that the GitBash is logging out before the next command "git archive...". Does anybody know if I can pass the command into GitBash and how? Mike Erik "C:\Program Files (x86)\Git\bin\sh.exe" --login -i -c "git archive master | tar -x -C $0" "%~1" rugg You can also run a shell

How to stop git via ssh on windows from resolving the wrong path?

爷,独闯天下 提交于 2019-11-27 06:16:00
问题 I have a windows 2003 box with an ssh server setup. I have msysgit (git version 1.6.2) installed both locally and on the server. The server has the following absolute path to my repos: e:\vc\git\myrepo.git when a user logs in he/she will be put in the following working directory: e:\vc\git\ When running the following cmd on my dev machine: git clone ssh://myuser@myip/myrepo.git testrepo I get the following error: fatal: ''/myrepo.git'' does not appear to be a git repository According to my

git: 'credential-cache' is not a git command

放肆的年华 提交于 2019-11-27 05:46:54
I followed these instructions to the letter, including the part about password caching. It seems like the instructions are wrong, because every time I git push origin master I get this error: git: 'credential-cache' is not a git command. See 'get --help'. ... at which point I am forced to enter my username and password. After doing so, I am presented with the same error message again, followed by the output from git push . Here is the contents of my .gitconfig file: [user] name = myusername email = myusername@myemaildomain.com [credential] helper = cache To be clear, after I installed Git and

Unable to resolve “unable to get local issuer certificate” using git on Windows with self-signed certificate

醉酒当歌 提交于 2019-11-27 05:46:42
I am using git on Windows. I installed the msysgit package. My test repository has a self signed certificate at the server. I can access and use the repository using http without problems. Moving to https gives the error "SSL Certificate problem: unable to get local issuer certificate". I have the self signed certificate installed in the Trusted Root Certification Authorities of my Windows 7 - client machine. I can browse to the https repository url in Internet Explorer with no error messages. This blog http://blogs.msdn.com/b/phkelley/archive/2014/01/20/adding-a-corporate-or-self-signed

List of all commands that cause git gc --auto

独自空忆成欢 提交于 2019-11-27 05:15:39
Is there a definitive list of commands anywhere that cause git gc --auto to run? The git-gc(1) man page simply states: --auto With this option, git gc checks whether any housekeeping is required; if not, it exits without performing any work. Some git commands run git gc --auto after performing operations that could create many loose objects. (emphasis added) I'm in the process of organising a large migration from SVN to Git. The overwhelming majority of users will be on Windows PCs, and a not-insignificant portion of them are non-technical. They will be using TortoiseGit (as it closely matches

Git error: fatal: unable to connect a socket (Invalid argument)

心不动则不痛 提交于 2019-11-27 05:06:22
问题 I've got msysGit (Git on Windows) working just fine on my home machine, but at work, where we are behind a Microsoft ISA proxy, I get the following error when I do a git clone: H:\>git clone git://github.com/akitaonrails/vimfiles.git Initialized empty Git repository in H:/vimfiles/.git/ github.com[0: 65.74.177.129]: errno=Invalid argument fatal: unable to connect a socket (Invalid argument) I've tried setting the http_proxy environment variable to: http://our-proxy-server:8088 I've set the

SSH Private Key Permissions using Git GUI or ssh-keygen are too open

不想你离开。 提交于 2019-11-27 04:59:28
问题 Recently I've been unable to clone or push to github, and I'm trying to find the root cause. This is on windows I have cygwin + git as well as msysgit. Msysgit was installed with the following options: OpenSSH Use Git from Windows Command Prompt That gives me 4 environments to try to use git in: Windows cmd prompt Powershell Git Bash Cygwin Somehow I've managed to get myself into a position where when I try to clone a repository using msysgit, cmd.exe, or Powershell, I get the following error

Hudson Git Plugin not working on windows

那年仲夏 提交于 2019-11-27 04:46:01
问题 I have msysgit installed with OpenSSH option. In Git bash, I can run ssh-agent, and it manages the passphrase for my ssh key. Is it possible for the Hudson Git plugin to use ssh-agent? Currently, it hangs when trying to clone, no doubt waiting for the passphrase to be entered. Thanks! 回答1: As mentioned in "Problem with Hudson + Git + Gitosis on windows", you need to make sure the Hudson job does set first a %HOME% environment variable. That value must refer to the directory where you can find

Clone works, remote push doesn't. Remote repository over copssh

你说的曾经没有我的故事 提交于 2019-11-27 04:40:46
I've "setup-a-msysgit-server-with-copssh-on-windows", following Tim Davis' guide and I was now learning how to use the git commands, following Jason Meridth's guide , and I have managed to get everything working fine, but now I can't pass the push command. I have set the server and the client on the same machine (for now), win7-x64. Here is some info of how things are set up: CopSSH Folder : C:/SSH/ Local Home Folder : C:/Users/rvc/ Remote Home Folder: C:/SSH/home/rvc/ # aka /cygdrive/c/SSH/home/rvc/ git remote rep : C:/SSH/home/rvc/myapp.git # empty rep At '/SSH/home/rvc/.bashrc' and 'Users

Which is the smarter git protocol, ssh or git(over ssh) or https protocol?

允我心安 提交于 2019-11-27 04:21:13
问题 Which is efficient? SSH:// or Git:// (File compression) I understand in Git , git protocol is smart because there is a protocol agent on both end of communication to compress the file transfer resulting in faster clone by efficiently using the network bandwidth. From an O'Reilly book I found the following statements. For secure, authenticated connections, the Git native protocol can be tunneled over an SSH connection using the following URL templates: ssh: //[user@]example.com[:port]/path/to