I've attached a small patch that allows msys to be run from a path that has spaces in it by quoting the path in a few places. To reproduce the problem I was seeing, all you have to do is create an msys environment in a path that has a space in it. e.g.: C:\Documents and Settings\user1\msys
I know the recommendation is to install to C:\msys, but I've run many, many msys/mingw programs that work fine without requiring them to be in C:\msys. This patch allows my environment to now be xcopy deployable. Which is a benefit for people in my project.
I'm on Windows 7, x86_64.
uname -a gives me: MINGW32_NT-6.1 DEV-PC1 1.0.15(0.47/3/2) 2010-07-06 22:04 i686 Msys
My environment should be up-to-date -- it was created this morning.