msysgit

I have a group of repos and I have a .mailmap file to combine user names. My .mailmap file works for all the repos, when it is in the root of each. I tried to put the file in my ~/.gitconfig file and it doesn't work. Im using Git for Windows and in my global .gitconfig file I added this: >> git config --global mailmap.file "~/.mailmap" Thats the command I used. Also tried the log shown below. [log] mailmap = ~/.mailmap [mailmap] file = C:/Documents and Settings/<username>/.mailmap Both lead to the same file location, but it doesn't seem to honor this file when using git-shortlog Any

I cloned a Git repository from Windows using msysgit (v1.7.7) on a network drive. Some files are marked on the repository to have mode 100755. Using the git bash tool from Windows, the ls -l command effectively shows the good permissions for those file. Now when I access the repository directory from Linux, those files have 644 permissions instead of 755. If I chmod them to 755 on the Linux side and go back to the git bash tool on Windows: the ls -l command still shows the files to have 755 permissions but the git diff command tells the files changed mode from 100755 to 100644 Any idea how to

I'm outputting to a terminal, but Git is not correctly detecting that I'm outputting to a terminal, for the purposes of coloring the output. My question is, what does git-config(1) really mean when it says "colors are used only when the output is to a terminal" (this phrase appears at the end of multiple config descriptions, such as for color.ui and color.branch)? In other words, how does Git decide whether or not it's outputting to a terminal, and how do I change my environment settings to inform Git that my terminal is indeed a terminal? Specifics: I'm using rxvt terminal with Cygwin on

If we open msysgit as administrator, we can use it as if we were root. However, it is often easier to open without administrator privileges. For example, for administrator privileges, you often have to go to Windows Explorer, the Start menu/screen, etc., and you can't do this from the taskbar. Sometimes, I'm too lazy to do all this, but I want to gain administrator privileges while in Bash. Is there a sudo - or su -like command or script, etc., for Git Bash? Going into cmd.exe , PowerShell , etc., then doing something like runas would work, if there's nothing else. you can't do it from the

I'm behind a proxy, and I'm quite new to git and I'm on Windows XP. I've been able to make a git push origin master work from msysgit but can't make it work in Cygwin with Cygwin's git. I configured git using the following command lines in both environments: git config --global user.name ... git config --global user.email ... git config --global http.proxy ... I'm playing with a test Github repo. The issue I have is with the following command line: git push origin master In msysgit, I have the following result: Writing objects: 100% (3/3), 222 bytes, done. Total 3 (delta 0), reused 0 (delta 0)

I am running Git-1.8.0-preview20121022 on Windows 7 and the install was with "Git Bash Only" (least intrusive to Windows cmd). When I open the Git Bash from the start menu shortcut, everything is fine with the history. But when the Git Bash here context menu (either the git-cheetah shell extension one or the simpler registry one) is what launched a session, the commands from that session are not saved to the .bash_history . How could figure out why this is happening? Or better yet, does someone know how to fix this? Steven Penny You should be able to fix this by adding this line to your ~/

I sometimes have to work in Windows, which often means using the Bash shell. If I am (for example) in vim ( not gvim ) with several files open, and I hit Ctrl Z to briefly go back to the shell and do something before returning to vim , instead of suspending my vim process Git Bash creates a new DOS shell. This is the last thing I'd ever want. Googling turns up nothing useful (at this point in time - YMMV in my future). What is going on? I sometimes have to work in Windows, which often means using the Git Bash shell. Good. Me too. If I am (for example) in vim (not gvim) with several files open,