Hi, On Thu, 23 Aug 2007, Theodore Tso wrote: > On Thu, Aug 23, 2007 at 11:31:56AM +0100, Johannes Schindelin wrote: > > > And that is _exactly_ where I fail to see benefits from. You only get > > the full power of C by using C. You only get the full power of all > > open source C programmers by using C. And you only get the full > > flexibility, speed, name-your-own-pet-peeve using C. > > Sure, but not all porcelein commands need the full power of C. Take > "git-gc" for example. It was a *very* short shell script before it was > rewritten to use C. That is right. It was short. > > I have seen boxes where the administrators locked down everything. > > And Cygwin _does_ need to write the registry, and there is _no_ easy > > way to have two independent Cygwin installs on the same machine. > > This is where MinGW/MSys really shines. > > So are you claiming that MingGW/MSys is so good that it has a perl/bash > that is fully Linux compatible, so that we don't need to convert our > various internal commands that are implemented in shell to C? I didn't > think that was a commonly held assessment... I did not even come close to saying that. MinGW/MSys has the advantage over Cygwin that you can have multiple installations. With different settings, in different places. However, since we are on Windows we have plenty of problems. Think fork(). Think "C:/srv" _not_ meaning a protocol. Think non-Git programs that have a non-POSIX idea of path names, or of passing a command line (including quoting). One problem we face ATM is that MSys apparently cannot be taught _not_ to mangle something as "repo.or.cz:/srv/git/something.git" into "repo.or.cz;C:\msysGit\srv/git/something.git". If we had no scripts, this would be a non-issue. Since no MSys would be involved. Anyway, I'd much rather use my time hacking than reading monster threads with more LOC than I will ever write in my life. And no, that "C" does not mean "code". Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
