From: Andrei Rybak <rybak.a.v@gmail.com>
To: "Øystein Walle" <oystwa@gmail.com>, gitster@pobox.com
Cc: git@vger.kernel.org, peff@peff.net, phillip.wood123@gmail.com
Subject: Re: [PATCH v3] branch, for-each-ref, tag: add option to omit empty lines
Date: Thu, 13 Apr 2023 01:44:23 +0200 [thread overview]
Message-ID: <a8b34639-60fb-8a23-d1d9-1ef4410a2ba4@gmail.com> (raw)
In-Reply-To: <20230407175316.6404-1-oystwa@gmail.com>
A couple of drive-by nitpicks about the commit message:
On 07/04/2023 19:53, Øystein Walle wrote:
> Subject: [PATCH v3] branch, for-each-ref, tag: add option to omit empty lines
>
> If the given format string expands to the empty string a newline is
> still printed it. This makes using the output linewise more tedious. For
It seems that a word is missing in the first sentence. Perhaps,
s/printed it/printed for it/
?
> example, git update-ref --stdin does not accept empty lines.
>
> Add options to branch and for-each-ref to not print these empty lines.
"git tag" is mentioned in the subject line, but not here.
> The default behavior remains the same.
>
> Signed-off-by: Øystein Walle <oystwa@gmail.com>
> ---
> Dang, you're right. But yes, it was a near-identical patch to
> builtin/tag.c. Along with a test, of course.
>
> I see you already applied the first of these patches so in this
> iteration there's only one.
>
> Documentation/git-branch.txt | 4 ++++
> Documentation/git-for-each-ref.txt | 4 ++++
> Documentation/git-tag.txt | 4 ++++
> builtin/branch.c | 6 +++++-
> builtin/for-each-ref.c | 7 +++++--
> builtin/tag.c | 6 +++++-
> t/t3203-branch-output.sh | 24 ++++++++++++++++++++++++
> t/t6300-for-each-ref.sh | 8 ++++++++
> t/t7004-tag.sh | 16 ++++++++++++++++
> 9 files changed, 75 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2023-04-12 23:44 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 ` [PATCH v2 0/2] branch, for-each-ref: add option to omit empty lines Øystein Walle
2023-04-06 17:08 ` [PATCH v2 1/2] ref-filter: remove unused ref_format member Ø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 [this message]
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=a8b34639-60fb-8a23-d1d9-1ef4410a2ba4@gmail.com \
--to=rybak.a.v@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=oystwa@gmail.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).