I've been working on a Git migration inside a fortune 50 primarily windows shop for about 6 months.
This line caught my eye:
"Some of its benefits fit well with the trends we see in software development: loosely coupled systems, distributed teams, lots of component reuse, incorporation of OSS, etc."
It's not a new trend. Nevertheless, I'm smitten that MS has acknowledged and embraced the model.
For us, the biggest issues with git on windows are:
1) SSH inconsistencies (cygwin/putty/msysgit/securecrt/etc) - I support users that use any combination of these.
2) Git implementations (cygwin/msysgit/git extensions/etc) and UIs all handle git and SSH differently. Users will typically have multiple copies of git installed and used, depending on context.
3) Support for HTTPS mode is inconsistent and in some cases non-existent. None of them can cache credentials.
To summarize; multiple git environments + multiple SSH environments + limited https support = pain.
This line caught my eye:
"Some of its benefits fit well with the trends we see in software development: loosely coupled systems, distributed teams, lots of component reuse, incorporation of OSS, etc."
It's not a new trend. Nevertheless, I'm smitten that MS has acknowledged and embraced the model.
For us, the biggest issues with git on windows are:
1) SSH inconsistencies (cygwin/putty/msysgit/securecrt/etc) - I support users that use any combination of these.
2) Git implementations (cygwin/msysgit/git extensions/etc) and UIs all handle git and SSH differently. Users will typically have multiple copies of git installed and used, depending on context.
3) Support for HTTPS mode is inconsistent and in some cases non-existent. None of them can cache credentials.
To summarize; multiple git environments + multiple SSH environments + limited https support = pain.