From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/5] minor ref-filter error-reporting bug-fixes
Date: Wed, 14 Dec 2022 11:18:19 -0500 [thread overview]
Message-ID: <Y5n3S7cnD7s/AIRL@coredump.intra.peff.net> (raw)
This series fixes a few small inconsistencies in the error-reporting
from ref-filter's atom parsers. Mostly I noticed this while dealing with
unused parameters in one of the parsers, which led to noticing a few
other small bugs. And I hope the result is a little cleaner, as it
should reduce the number of strings needing translation.
[1/5]: ref-filter: reject arguments to %(HEAD)
[2/5]: ref-filter: factor out "%(foo) does not take arguments" errors
[3/5]: ref-filter: factor out "unrecognized %(foo) arg" errors
[4/5]: ref-filter: truncate atom names in error messages
[5/5]: ref-filter: convert email atom parser to use err_bad_arg()
ref-filter.c | 44 +++++++++++++++++++++++++++++------------
t/t6300-for-each-ref.sh | 18 +++++++++++++++++
2 files changed, 49 insertions(+), 13 deletions(-)
-Peff
next reply other threads:[~2022-12-14 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 16:18 Jeff King [this message]
2022-12-14 16:18 ` [PATCH 1/5] ref-filter: reject arguments to %(HEAD) Jeff King
2022-12-14 16:19 ` [PATCH 2/5] ref-filter: factor out "%(foo) does not take arguments" errors Jeff King
2022-12-14 19:51 ` Taylor Blau
2022-12-14 20:03 ` Taylor Blau
2022-12-14 20:28 ` Jeff King
2022-12-14 16:20 ` [PATCH 3/5] ref-filter: factor out "unrecognized %(foo) arg" errors Jeff King
2022-12-14 16:23 ` [PATCH 4/5] ref-filter: truncate atom names in error messages Jeff King
2022-12-14 20:05 ` Taylor Blau
2022-12-14 20:39 ` Jeff King
2022-12-14 16:24 ` [PATCH 5/5] ref-filter: convert email atom parser to use err_bad_arg() Jeff King
2022-12-14 20:05 ` [PATCH 0/5] minor ref-filter error-reporting bug-fixes Taylor Blau
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=Y5n3S7cnD7s/AIRL@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
/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).