From: "Louis Sautier via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Louis Sautier <sautier.louis@gmail.com>,
Louis Sautier <sautier.louis@gmail.com>
Subject: [PATCH] pretty: fix a typo in the documentation for %(trailers)
Date: Wed, 12 May 2021 11:18:02 +0000 [thread overview]
Message-ID: <pull.1023.git.git.1620818283024.gitgitgadget@gmail.com> (raw)
From: Louis Sautier <sautier.louis@gmail.com>
This just changes occurance to occurrence.
Signed-off-by: Louis Sautier <sautier.louis@gmail.com>
---
pretty: fix a typo in the documentation for %(trailers)
Hi,
Here is a very minor change: occurance → occurrence ?
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1023%2Fsbraz%2Ftypo-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1023/sbraz/typo-v1
Pull-Request: https://github.com/git/git/pull/1023
Documentation/pretty-formats.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/pretty-formats.txt b/Documentation/pretty-formats.txt
index cd697f508c53..ea9b26c3f734 100644
--- a/Documentation/pretty-formats.txt
+++ b/Documentation/pretty-formats.txt
@@ -271,7 +271,7 @@ endif::git-rev-list[]
`trailers` string may be followed by a colon
and zero or more comma-separated options.
If any option is provided multiple times the
- last occurance wins.
+ last occurrence wins.
+
The boolean options accept an optional value `[=<BOOL>]`. The values
`true`, `false`, `on`, `off` etc. are all accepted. See the "boolean"
base-commit: a0f521b56c724f4e21eef1cec2d456b1dbd72c10
--
gitgitgadget
next reply other threads:[~2021-05-12 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 11:18 Louis Sautier via GitGitGadget [this message]
2021-05-12 13:12 ` [PATCH] pretty: fix a typo in the documentation for %(trailers) Bagas Sanjaya
2021-05-12 22:48 ` Junio C Hamano
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=pull.1023.git.git.1620818283024.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=sautier.louis@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.