From: Jeff King <peff@peff.net>
To: Tarmigan <tarmigan+git@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Typo in RelNotes.
Date: Thu, 12 Jun 2008 02:14:28 -0400 [thread overview]
Message-ID: <20080612061428.GA28696@sigill.intra.peff.net> (raw)
In-Reply-To: <905315640806112206g4df6ce11h2a98412223e13fdd@mail.gmail.com>
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
prev parent reply other threads:[~2008-06-12 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 2:38 [PATCH] Typo in RelNotes Mikael Magnusson
2008-06-12 3:59 ` Tarmigan
2008-06-12 4:53 ` Jeff King
2008-06-12 5:06 ` Tarmigan
2008-06-12 6:14 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080612061428.GA28696@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tarmigan+git@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).