On Wed, Jun 11, 2008 at 10:06:13PM -0700, Tarmigan wrote: > > Maybe I am blind, but I don't see a typo. Are you referring to tformat, > > which looks like a typo, but is actually correct? > > Oops you're right. That's what I was thinking of. Junio's commit > message explains it well. Should something be added to the man page > about it? How about this? I worry that the perl in the example is unnecessarily complex, but I couldn't think of a simpler way to show "in this one, the trailing newline is missing". So I am open to suggestions. -- >8 -- document --pretty=tformat: option This was introduced in 4da45bef, but never documented anywhere. --- Documentation/pretty-formats.txt | 21 +++++++++++++++++++++ 1 files changed, 21 insertions(+), 0 deletions(-) diff --git a/Documentation/pretty-formats.txt b/Documentation/pretty-formats.txt index e8bea3e..14a2665 100644 --- a/Documentation/pretty-formats.txt +++ b/Documentation/pretty-formats.txt @@ -124,3 +124,24 @@ The placeholders are: - '%m': left, right or boundary mark - '%n': newline - '%x00': print a byte from a hex code + +* 'tformat:' ++ +The 'tformat:' format works exactly like 'format:', except that it +provides "terminator" semantics instead of "separator" semantics. In +other words, each commit has the message separator (usually a newline) +appended, rather than placed between entries. This means that the final +entry of a single-line format will be properly terminated with a new +line, just as the "oneline" format does. For example: ++ +--------------------- +$ git log -2 --pretty=format:%h 4da45bef \ + | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/' +4da45be +7134973 -- NO NEWLINE + +$ git log -2 --pretty=tformat:%h 4da45bef \ + | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/' +4da45be +7134973 +--------------------- -- 1.5.6.rc2.168.g23af0b.dirty -- 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
