Re: [RFC PATCH] builtin:tag:verify_tag: allow gpg output + pretty

From: Jeff King <peff@peff.net>
Date: Apr 22, 2019, 16:02 UTC
Message-ID: <20190422160211.GB9680@sigill.intra.peff.net>
In-Reply-To: <20190422154655.sxyrkee7rnywoh2w@LykOS.localdomain>

On Mon, Apr 22, 2019 at 11:46:56AM -0400, Santiago Torres Arias wrote:

Show 8 quoted lines

> > In some ways I'm less concerned about verify-tag, though, because the
> > point is that it should be scriptable. And scraping gpg's stderr is not
> > ideal there. We should be parsing --status-fd ourselves and making the
> > result available via format specifier, similar to the way "log
> > --format=%G?" works.
> 
> I think that would be great, as we could make it simpler for verifiers
> to parse gpg output.

Alternatively, we could make it an option to dump the --status-fd output to stderr (or to a custom fd). That still leaves the caller with the responsibility to parse gpg's output, but at least they're parsing the machine-readable bits and not the regular human-readable stderr.

-Peff