Junio C Hamano <gitster@xxxxxxxxx> writes: > Jeff King <peff@xxxxxxxx> writes: > >> On Fri, Feb 12, 2016 at 10:40:48PM +0100, SZEDER Gábor wrote: >> >>> * It would swallow even those errors that we are interested in, >>> e.g. (note the missing quotes around $foo): >>> [...] >>> * I often find myself tracing/debugging the completion script >>> through stderr by scattering >>> >>> echo >&2 "foo: '$foo'" >> >> One alternative to deal with these would be to add a flag to >> conditionally turn off stderr, and then leave it on during normal >> operation and disable it (letting everything through, including whatever >> random cruft git commands produce) for debugging. >> >> But... >> >>> * I have a WIP patch series that deals with errors from git >>> commands. >> >> I'm happy to wait and see what this patch looks like (and generally >> happy to defer to you on maintenance issues for completion, as you are >> much more likely than me to be the one fixing things later on :) ). >> >> -Peff > > Likewise on both counts. So, have we decided to wait, or we'd rather apply the band-aid in the meantime? I can go either way, just double checking as I noticed this thread while updating my leftover bits list. Thanks. -- 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