On Wed, Aug 28, 2013 at 04:18:03PM -0400, Jeff King wrote: > On Wed, Aug 28, 2013 at 01:05:38PM -0700, Junio C Hamano wrote: > > > What are our plans to help existing scripts people have written over > > time, especially before "status -s" was invented, that will be > > broken by use of this? > > I thought that our response to parsing the long output of "git status" > was always "you are doing it wrong". The right way has always been to > run the plumbing tools yourself, followed eventually by the --porcelain > mode to "git status" being blessed as a convenient plumbing. > > I will not say that people might not do it anyway, but at what point do > we say "you were warned"?
It already has changed. At cPanel, we had code that broke with a new version of git because the output of git status changed between 1.7.11 and 1.8.3. We fixed it to use --porcelain and had no problems. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
