From: "John Cai via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: John Cai <johncai86@gmail.com>, John Cai <johncai86@gmail.com>
Subject: [PATCH 4/4] doc: add docs for newlineafter flag
Date: Fri, 29 Oct 2021 21:15:27 +0000 [thread overview]
Message-ID: <57b2079f30a3b8cbaf83c93510abd5b1ad7fff61.1635542128.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1065.git.1635542128.gitgitgadget@gmail.com>
From: John Cai <johncai86@gmail.com>
Provide documentation for --newlineafter flag
Signed-off-by: John Cai <johncai86@gmail.com>
---
Documentation/pretty-options.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/pretty-options.txt b/Documentation/pretty-options.txt
index b3af8506086..7de51c660fe 100644
--- a/Documentation/pretty-options.txt
+++ b/Documentation/pretty-options.txt
@@ -32,6 +32,10 @@ people using 80-column terminals.
This is a shorthand for "--pretty=oneline --abbrev-commit"
used together.
+--newlineafter[=(decorations)]
+ Used in conjunction with --pretty=oneline to add a line break after
+ decorations
+
--encoding=<encoding>::
Commit objects record the character encoding used for the log message
in their encoding header; this option can be used to tell the
--
gitgitgadget
next prev parent reply other threads:[~2021-10-29 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 21:15 [PATCH 0/4] Flag to add a newline after decorations for --oneline log output John Cai via GitGitGadget
2021-10-29 21:15 ` [PATCH 1/4] oneline: parse --newlineafter flag John Cai via GitGitGadget
2021-10-29 21:15 ` [PATCH 2/4] oneline: print newline after decorations if flag provided John Cai via GitGitGadget
2021-10-29 21:15 ` [PATCH 3/4] oneline: test for --newlineafter feature John Cai via GitGitGadget
2021-10-29 21:15 ` John Cai via GitGitGadget [this message]
2021-11-12 16:27 ` [PATCH 0/4] Flag to add a newline after decorations for --oneline log output Christian Couder
2021-11-21 1:19 ` John Cai
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=57b2079f30a3b8cbaf83c93510abd5b1ad7fff61.1635542128.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=johncai86@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).