From: Felipe Contreras Date: Wed, 28 Nov 2012 00:10:34 GMT Subject: Re: Python extension commands in git - request for policy change Message-ID: In-Reply-To: <20121127143510.GA15831@google.com> On Tue, Nov 27, 2012 at 3:35 PM, Magnus Bäck wrote: > On Sunday, November 25, 2012 at 06:40 EST, > Felipe Contreras wrote: > >> On Sun, Nov 25, 2012 at 11:44 AM, Michael Haggerty >> wrote: > > [...] > >> > On the contrary, there is *constant* traffic on the mailing list >> > about incompatibilities between different shell implementations (sh, >> > dash, bash, etc), not to mention those in other utilities (sed, >> > grep, etc) that one is forced to work with in shell scripts. >> > Compatibility is a *huge* pain when developing shell code for git. >> > The fact that users typically don't encounter such problems is due >> > to the hard work of POSIX lawyers on the mailing list correcting the >> > compatibility errors of mortal programmers. >> >> *Theoretical* incompatibilities on probably obscure systems. *I* have >> never seen such compatibility issues *in practice*. > > While "constant traffic" probably overstates the issue, these are not > theoretical problems. I recall at least three cases in the last year > or so where Git has seen breakage with Solaris or Mac OS X because > of sed or tr incompatibilities, and I don't even read this list that > thoroughly. Most of the *constant* traffic is about *theoretical* incompatibilities, how much of that are real incompatibilities, it's not known. _Some_ of the traffic is about real incompatibilities, sure, but you could count only three cases *in a year*. It's not a huge amount. And then, how man this year? Also, I would like references to those incompatibilities. Cheers. -- Felipe Contreras