From: "Øystein Walle" <oystwa@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, phillip.wood123@gmail.com, peff@peff.net,
oystwa@gmail.com
Subject: [PATCH v2 0/2] branch, for-each-ref: add option to omit empty lines
Date: Thu, 6 Apr 2023 19:08:35 +0200 [thread overview]
Message-ID: <20230406170837.10060-1-oystwa@gmail.com> (raw)
In-Reply-To: <xmqq4jq0hp1i.fsf@gitster.g>
Changes since v1:
- Improved commit message in 1/2,
- Stopped considering flag combinations as an error, which greatly
simplified the logic,
- Improved weird test file generation,
- Removed short option and renamed long option,
- Changed conditions to check the string length before the flag, which
imo. reads better.
Øystein Walle (2):
ref-filter: remove unused ref_format member
branch, for-each-ref: add option to omit empty lines
Documentation/git-branch.txt | 4 ++++
Documentation/git-for-each-ref.txt | 4 ++++
ref-filter.h | 1 -
builtin/branch.c | 6 +++++-
builtin/for-each-ref.c | 7 +++++--
ref-filter.c | 1 -
t/t3203-branch-output.sh | 24 ++++++++++++++++++++++++
t/t6300-for-each-ref.sh | 8 ++++++++
8 files changed, 50 insertions(+), 5 deletions(-)
--
2.20.1
next prev parent reply other threads:[~2023-04-06 17:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 11:21 [PATCH 0/2] branch, for-each-ref: add option to omit empty lines Øystein Walle
2023-03-30 11:21 ` [PATCH 1/2] ref-filter: remove unused ref_format member Øystein Walle
2023-03-30 15:21 ` Junio C Hamano
2023-03-30 15:25 ` Junio C Hamano
2023-03-31 10:37 ` Øystein Walle
2023-03-31 10:57 ` ZheNing Hu
2023-03-31 16:19 ` Junio C Hamano
2023-04-06 17:08 ` Øystein Walle [this message]
2023-04-06 17:08 ` [PATCH v2 " Øystein Walle
2023-04-06 17:08 ` [PATCH v2 2/2] branch, for-each-ref: add option to omit empty lines Øystein Walle
2023-04-06 18:24 ` [PATCH v2 0/2] " Junio C Hamano
2023-04-07 17:53 ` [PATCH v3] branch, for-each-ref, tag: " Øystein Walle
2023-04-07 18:48 ` Junio C Hamano
2023-04-12 23:44 ` Andrei Rybak
2023-04-13 7:17 ` Øystein Walle
2023-04-13 15:13 ` Junio C Hamano
2023-03-30 11:21 ` [PATCH 2/2] branch, for-each-ref: " Øystein Walle
2023-03-30 15:54 ` Junio C Hamano
2023-03-30 18:25 ` Jeff King
2023-03-30 18:54 ` Junio C Hamano
2023-03-31 8:32 ` Øystein Walle
2023-03-31 15:57 ` Junio C Hamano
2023-03-30 17:21 ` Junio C Hamano
2023-03-31 16:33 ` Phillip Wood
2023-03-31 17:17 ` Junio C Hamano
2023-04-06 16:55 ` Øystein Walle
2023-04-06 17:12 ` Jeff King
2023-04-06 18:20 ` Junio C Hamano
2023-04-10 19:56 ` Jeff King
2023-04-06 18:07 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230406170837.10060-1-oystwa@gmail.com \
--to=oystwa@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=phillip.wood123@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).