[PATCH] Typo in RelNotes.

Subsystems: documentation, the rest

DORMANTno replies

5 messages, 3 authors, 2016-06-15 · open the first message on its own page

[PATCH] Typo in RelNotes.

From: Mikael Magnusson <hidden>
Date: 2016-06-15 22:44:43

Signed-off-by: Mikael Magnusson <redacted>

---

This is the first patch I send for git so I hope i didn't do anything silly :).

  Documentation/RelNotes-1.5.6.txt |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/RelNotes-1.5.6.txt b/Documentation/RelNotes-1.5.6.txt
index a79e4b9..ac4881e 100644
--- a/Documentation/RelNotes-1.5.6.txt
+++ b/Documentation/RelNotes-1.5.6.txt
@@ -70,7 +70,7 @@ Updates since v1.5.5

  * "git init --bare" is a synonym for "git --bare init" now.

-* "git gc --auto" honors a new pre-aut-gc hook to temporarily disable it.
+* "git gc --auto" honors a new pre-auto-gc hook to temporarily disable it.

  * "git log --pretty=tformat:<custom format>" gives a LF after each entry,
    instead of giving a LF between each pair of entries which is how
-- 
1.5.5.GIT


--
Mikael Magnusson

Re: [PATCH] Typo in RelNotes.

From: Tarmigan <hidden>
Date: 2016-06-15 22:44:43

On Wed, Jun 11, 2008 at 7:38 PM, Mikael Magnusson [off-list ref] wrote:
 * "git init --bare" is a synonym for "git --bare init" now.

-* "git gc --auto" honors a new pre-aut-gc hook to temporarily disable it.
+* "git gc --auto" honors a new pre-auto-gc hook to temporarily disable it.

 * "git log --pretty=tformat:<custom format>" gives a LF after each entry,
  instead of giving a LF between each pair of entries which is how
Any interest in fixing the typo on the next line while you're at it?

-Tarmigan

Re: [PATCH] Typo in RelNotes.

From: Jeff King <hidden>
Date: 2016-06-15 22:44:43

On Wed, Jun 11, 2008 at 08:59:37PM -0700, Tarmigan wrote:
On Wed, Jun 11, 2008 at 7:38 PM, Mikael Magnusson [off-list ref] wrote:
quoted
 * "git init --bare" is a synonym for "git --bare init" now.

-* "git gc --auto" honors a new pre-aut-gc hook to temporarily disable it.
+* "git gc --auto" honors a new pre-auto-gc hook to temporarily disable it.

 * "git log --pretty=tformat:<custom format>" gives a LF after each entry,
  instead of giving a LF between each pair of entries which is how
Any interest in fixing the typo on the next line while you're at it?
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?

-Peff

Re: [PATCH] Typo in RelNotes.

From: Tarmigan <hidden>
Date: 2016-06-15 22:44:43

On Wed, Jun 11, 2008 at 9:53 PM, Jeff King [off-list ref] wrote:
On Wed, Jun 11, 2008 at 08:59:37PM -0700, Tarmigan wrote:
quoted
On Wed, Jun 11, 2008 at 7:38 PM, Mikael Magnusson [off-list ref] wrote:
quoted
 * "git init --bare" is a synonym for "git --bare init" now.

-* "git gc --auto" honors a new pre-aut-gc hook to temporarily disable it.
+* "git gc --auto" honors a new pre-auto-gc hook to temporarily disable it.

 * "git log --pretty=tformat:<custom format>" gives a LF after each entry,
  instead of giving a LF between each pair of entries which is how
Any interest in fixing the typo on the next line while you're at it?
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?

-Tarmigan

Re: [PATCH] Typo in RelNotes.

From: Jeff King <hidden>
Date: 2016-06-15 22:44:43

On Wed, Jun 11, 2008 at 10:06:13PM -0700, Tarmigan wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help