Re: [PATCH 4/5] interpret-trailers: add an option to normalize output

From: Jeff King <peff@peff.net>
Date: Aug 10, 2017, 21:10 UTC
Message-ID: <20170810211039.okpwglvcmkngzri2@sigill.intra.peff.net>
In-Reply-To: <CAP8UFD08oyY9eK-0Ydm2qh2etvc2_QGc0ujNswGUgUumwhy4+w@mail.gmail.com>

On Thu, Aug 10, 2017 at 11:06:40PM +0200, Christian Couder wrote:

Show 13 quoted lines

> >> Related to this, I wonder if people might want to "normalize" in
> >> different ways later. If that happens, we might regret having called
> >> this option "--normalize" instead of "--one-per-line" for example.
> >
> > What is normal?
> >
> > Maybe --style=[one-line, wrapped:72, rfc, json, xml, ...]
> > then?
> 
> Yeah, we could go there right now (using perhaps "--pretty" or
> "--format" instead of "--style", so that we are more consistent with
> other commands), but on the other hand we don't know yet if the other
> formats will really be needed.

But some of those things are not 1:1 mappings with normalization. For instance, --json presumably implies --only-trailers. Or are we proposing to break the whole commit message down into components and output it all as json?

-Peff