OriginalGooglecodePage
Git for Windows http://msysgit.googlecode.com/files/msysgitlogo.png
Git is a powerful distributed Source Code Management tool.
If you just want to use Git to do your version control in Windows, you will need to download Git for Windows. There's both an installable and a portable version available. *Note:* Git for Windows is a project run by volunteers, so if you want it to improve, *volunteer*!
If you want to download and install the complete source code (including C compiler) to start hacking on Git for Windows itself, you will need to install the full development system which is called msysGit. Please read install msysGit to get detailed information.
All featured downloads are also linked from the sidebar on the left.
More information:
* How to [https://github.com/msysgit/msysgit/wiki/InstallMSysGit install msysGit] or [https://github.com/msysgit/msysgit/wiki/UpdatingMSysGit update msysGit] * [https://github.com/msysgit/msysgit/wiki/GitCheetah Git-Cheetah] * The archives of the [https://github.com/msysgit/msysgit/wiki/MSysGitHerald msysGit Herald]
First, install msysGit. No worry, this is easier than you think. Downloading and executing it will give you a working development environment and compile Git automatically!
Please note that there are not enough contributors to the msysGit project to offer commercial-grade support; if you do not have the means to fix your problems (possibly with valuable advice from the msysgit@googlegroups.com), or to entice people who can fix them, it is unlikely that your problem gets solved.
See also the GetHelp page on our Wiki.
First, install msysGit. No worry, this is easier than you think. Downloading and executing it will give you a working development environment and compile Git automatically!
Testing and reporting bugs is a big help however you *MUST* do your research. If the solution to your problem can be Googled easily, well, it can be Googled easily. Check the mailing list. When you raise a bug you are expected to be available to provide further information and to followup with testing. If you simply raise a bug and then vanish, you will simply have wasted time and are unlikely to get help. If you really want to ensure something is fixed then provide a patch or push to the 'mob' branch as below.
If you made some changes to our development evironment, you can contribute them back by forking on GitHub.
If instead, you made changes to Git for Windows (i.e. in the directory /git/ in the development environment), you can contribute them back by forking our git repository on GitHub.
If you want to report a bug in Git itself, git-svn or git-gui (non-Windows-specific), please send a mail to git@vger.kernel.org.
If you want to report a bug in Git for Windows (Windows-specific), or in msysGit (also Windows-specific), please send a message to msysgit@googlegroups.com, but be aware that posts by non-members, as well as the first post of new members, are moderated. And please be prepared to put a considerable effort into solving the issue if you want others to put in the same amount of effort.
If your question is not Windows-specific, you might want to send it to the git@vger.kernel.org instead (or at least in addition to the msysGit mailing list).