From: "John Cai via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: John Cai <johncai86@gmail.com>
Subject: [PATCH 0/4] Flag to add a newline after decorations for --oneline log output
Date: Fri, 29 Oct 2021 21:15:23 +0000 [thread overview]
Message-ID: <pull.1065.git.1635542128.gitgitgadget@gmail.com> (raw)
Add a flag --newlineafter to be able to pass in "decorations" to enable a
nicer format for the --oneline output so the commit subjects are aligned
when decorations are printed.
0b96396ef5ff7a3a01e137b3735893c970759dfa (HEAD -> jc/two-line-pretty-decoration, john-cai/jc/two-line-pretty-decoration)
Improve UX for oneline with decorations
e9e5ba39a78c8f5057262d49e261b42a8660d5b9 (origin/master, origin/HEAD, master)
The fifteenth batch
c6fc44e9bf85dc02f6d33b11d9b5d1e10711d125 Merge branch 'ab/test-lib-diff-cleanup'
63ec2297d26155adb0e38745bf2284cd663add8e Merge branch 'ab/fix-make-lint-docs'
original thread in
https://lore.kernel.org/git/CA+55aFwT2HUBzZO8Gpt9tHoJtdRxv9oe3TDoSH5jcEOixRNBXg@mail.gmail.com/T/#t
John Cai (4):
oneline: parse --newlineafter flag
oneline: print newline after decorations if flag provided
oneline: test for --newlineafter feature
doc: add docs for newlineafter flag
Documentation/pretty-options.txt | 4 ++++
builtin/log.c | 25 +++++++++++++++++++++++++
log-tree.c | 20 ++++++++++++++++----
log-tree.h | 7 +++++--
pretty.c | 4 ++--
revision.h | 4 ++++
t/t4205-log-pretty-formats.sh | 10 ++++++++++
7 files changed, 66 insertions(+), 8 deletions(-)
base-commit: e9e5ba39a78c8f5057262d49e261b42a8660d5b9
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1065%2Fjohn-cai%2Fjc%2Ftwo-line-pretty-decoration-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1065/john-cai/jc/two-line-pretty-decoration-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1065
--
gitgitgadget
next 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 John Cai via GitGitGadget [this message]
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 ` [PATCH 4/4] doc: add docs for newlineafter flag John Cai via GitGitGadget
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=pull.1065.git.1635542128.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).