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 3/4] oneline: test for --newlineafter feature
Date: Fri, 29 Oct 2021 21:15:26 +0000 [thread overview]
Message-ID: <ea9ba5d0114d43ab275de47e20e066880aabb931.1635542128.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1065.git.1635542128.gitgitgadget@gmail.com>
From: John Cai <johncai86@gmail.com>
Signed-off-by: John Cai <johncai86@gmail.com>
---
t/t4205-log-pretty-formats.sh | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/t/t4205-log-pretty-formats.sh b/t/t4205-log-pretty-formats.sh
index 5865daa8f8d..847426f8af0 100755
--- a/t/t4205-log-pretty-formats.sh
+++ b/t/t4205-log-pretty-formats.sh
@@ -576,6 +576,16 @@ test_expect_success 'clean log decoration' '
test_cmp expected actual1
'
+test_expect_success 'oneline with --newlineafter=decorations' '
+ git checkout -b newlineafter &&
+ >baz &&
+ git add baz &&
+ git commit -m "decorations" &&
+ git log --pretty=format:"%h%d%n%>(18) %s%n" --max-count=1 >expect &&
+ git log --oneline --decorate --max-count=1 --newlineafter=decorations >actual &&
+ test_cmp expect actual
+'
+
cat >trailers <<EOF
Signed-off-by: A U Thor <author@example.com>
Acked-by: A U Thor <author@example.com>
--
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 ` John Cai via GitGitGadget [this message]
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=ea9ba5d0114d43ab275de47e20e066880aabb931.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 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.