Hmmm... okay so switching from Perforce to git only changes things for a select few who actually commit? So what's the big deal?

While the Perl for Linux camp enthusiasts are probably dribbling with uncontrolled glee about now being able to fiddle with git when fiddling with Perl... what about the Perl for Win32 camp? According to Wikipedia about git on Win32: msysgit: "While somewhat slower than the Linux version, it is acceptably fast and is reported to be usable in production, with only minor awkwardness. In particular, some commands are not yet available from the GUIs, and must be invoked from the command line." CYGWIN git: "Regardless, many people find a Cygwin installation too large and invasive for typical Windows use." At least with Perforce it was equally easy to get Perforce up and running on Linux or Win32 boxes. Typically you'd just have to copy one executable "p4" or if you prefer the GUI then additionally "p4v". I can't help feeling that switching to "currently-Win32-neglected" git could possibly harm one of Perl's most attractive qualities; that many modules work cross platform. Surely it would be more prudent for the Perl maintainers to wait until Win32 git is more mature etc?

While the Perl for Linux camp enthusiasts are probably dribbling with uncontrolled glee about now being able to fiddle with git when fiddling with Perl... what about the Perl for Win32 camp? According to Wikipedia about git on Win32: msysgit: "While somewhat slower than the Linux version, it is acceptably fast and is reported to be usable in production, with only minor awkwardness. In particular, some commands are not yet available from the GUIs, and must be invoked from the command line." CYGWIN git: "Regardless, many people find a Cygwin installation too large and invasive for typical Windows use." At least with Perforce it was equally easy to get Perforce up and running on Linux or Win32 boxes. Typically you'd just have to copy one executable "p4" or if you prefer the GUI then additionally "p4v". I can't help feeling that switching to "currently-Win32-neglected" git could possibly harm one of Perl's most attractive qualities; that many modules work cross platform. Surely it would be more prudent for the Perl maintainers to wait until Win32 git is more mature etc?