> I really do not see why msysgit should even look in the path for its > tools.
You're probably right, in theory msysGit could find out where it is installed (even without looking at any registry keys) and then spawn any needed executabled from that directory (or its sub-directories) only. However, msysGit and Git are aiming to use the same code base, and my guess is that the above is not very "Linux-ish", so it would not make it into the Git sources. > from the Windows command prompt instead of bash. grep, sed, awk, > unix2dos, dos2unix, wc, ln, nm... all are great tools and we like having > them available in the regular Windows command prompt. We're also mainly Windows developers at our company. But we're simply using Cygwin Bash *instead* of the Windows command prompt. As you can do everything from Cygwin Bash that you can do from the Windows command prompt (incl. launching BAT and CMD files), I do not really see the point of using the Windows command prompt at all anymore. I guess I would miss such simple things like Bash completion too soon :-) > From the Windows user's perspective... both git and cygwin tools are > just command-line tools one can call. And there should be no need for > them to cause conflicts with each other. I think it's quite natural that you get conflicts if you put directories that contain executables with same names into PATH :-) -- Sebastian Schuberth
