Thread (60 messages) read the whole thread 60 messages, 6 authors, 2017-08-17

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

From: Jeff King <hidden>
Date: 2017-08-10 23:10:45

On Fri, Aug 11, 2017 at 12:02:49AM +0100, Ramsay Jones wrote:
quoted
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?
Hmm, to me the operation wasn't so much a normalization, rather
it was an --unfold (or maybe --un-fold ;-D). I suppose going in
the other direction could be --fold=72, or some such.
But I really don't want callers to think of it as "unfold". I want it to
be "turn this into something I can parse simply". Hence if we were to
find another case where the output is irregular, I'd feel comfortable
calling that a bug and fixing it (one that I suspect but haven't tested
is that alternate separators probably should all be converted to
colons).
[blue is my favourite colour ... :-P ]
Yes, I'm feeling that, too. :-/

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help