From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: "Aleksandr Makarov" <aleksandr.o.makarov@gmail.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 0/3] un-break for-each-ref --ignore-case
Date: Mon, 2 Jul 2018 17:11:00 -0400 [thread overview]
Message-ID: <20180702211100.GA20885@sigill.intra.peff.net> (raw)
This is a follow-up to this patch last September:
https://public-inbox.org/git/79c946a2-532e-1c9b-7bf2-1f1ccbff721e@gmail.com/
The patch was the right thing to do, but:
1. It needed a commit message.
2. It needed a signoff.
3. It needed a test, which then showed that there was _another_ bug. :)
This fixes 1 and 3, and the extra bug. I've added my signoff to
Aleksandr's patch, as I think it is a trivial enough change to fall
under the DCO part b. But Aleksandr, if you can give your explicit
sign-off to include the patch in the project, that would be better
still.
[1/3]: t6300: add a test for --ignore-case
[2/3]: for-each-ref: consistently pass WM_IGNORECASE flag
[3/3]: ref-filter: avoid backend filtering with --ignore-case
ref-filter.c | 11 ++++++++++-
t/t6300-for-each-ref.sh | 11 +++++++++++
2 files changed, 21 insertions(+), 1 deletion(-)
-Peff
next reply other threads:[~2018-07-02 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 21:11 Jeff King [this message]
2018-07-02 21:11 ` [PATCH 1/3] t6300: add a test for --ignore-case Jeff King
2018-07-02 21:11 ` [PATCH 2/3] for-each-ref: consistently pass WM_IGNORECASE flag Jeff King
2018-07-02 21:12 ` [PATCH 3/3] ref-filter: avoid backend filtering with --ignore-case Jeff King
2018-07-02 21:30 ` Eric Sunshine
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=20180702211100.GA20885@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=aleksandr.o.makarov@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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).