On Thu, Aug 10, 2017 at 1:03 AM, Jeff King <p...@peff.net> wrote: > The point of "--only-trailers" is to give a caller an output > that's easy for them to parse. Getting rid of the > non-trailer material helps, but we still may see more > complicated syntax like whitespace continuation. Let's add > an option to normalize the output into one "key: value" line > per trailer. > > As a bonus, this could be used even without --only-trailers > to clean up unusual formatting in the incoming data.
This is useful for the parsing part, but for the writing part we'd rather want to have the opposite thing, such as '--line-break=rfc822'. But this doesn't have to be part of this series. With this in mind, I do not quite understand the latter use case how you would use normalized trailers without --only-trailers?
