Git for Windows provides a BASH emulation used to run Git from the command line. *NIX users should feel right at home, as the BASH emulation behaves just like the “git” command in LINUX and UNIX environments.

Some developers want to start git-bash (of Git for Windows SDK) with a different language. To achieve this in windows following command could be placed inside the launcher: C:\Windows\System32\cmd.exe /c "set LANG=en_GB && start C:\git-sdk-64\git-bash.exe && exit" replace en_GB with your preferred locale.

Git Bash promises a full-featured Bash, not BusyBox’ ash, with Git for Windows, it is even more likely that users may want to use functionality in their hooks and/or aliases which is not supported by BusyBox.

When starting Git Bash is already slow, edit the file <GIT_HOME>/etc/profile and insert a set -x somewhere at the top. This command will tell Bash to echo the commands it is executing so that you can find out which commands are slow and investigate more closely in that direction.

Interactive Bash/GDB. Sometimes it is a pretty interesting option to investigate an intermediate state of a working directory in the middle of a test regression by starting an interactive shell right at that moment. There is just one problem with inserting bash && into the test’s code: Git automatically redirects stdin/stdout/stderr.

In either a bash window or a cmd window, enter the .ssh directory found in your home directory. Type ssh-keygen and you will be prompted like this: Generating public/private rsa key pair.

You need to fetch the latest version of the Git sources - just run the command sdk init git. After that, if you just want to build an installer from the latest development, you are ready to go. You can open the Git for Windows SDK shell by double clicking git-bash.exe in the install folder.

You can inspect the source code at the current code location using the l command (or specify a line number or even a file and a line number like so: l git.c:709, or a function name, like so: l run_builtin).