From: Christian Couder <christian.couder@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Christian Couder <chriscool@tuxfamily.org>
Subject: [PATCH v2 0/2] Add support for %(contents:size) in ref-filter
Date: Thu, 2 Jul 2020 16:08:43 +0200 [thread overview]
Message-ID: <20200702140845.24945-1-chriscool@tuxfamily.org> (raw)
This is version 2 of a very small patch series to teach ref-filter
about %(contents:size).
Version 1 consisted on a single patch which is available here:
https://lore.kernel.org/git/20200701132308.16691-1-chriscool@tuxfamily.org/
As suggested by Peff, I added a preparatory patch (1/2) to clean up
the documentation about the %(contents:XXXX) format specifiers.
The other difference with V1 is that there are more tests in patch
2/2. These new tests required a small helper function to be
introduced.
Christian Couder (2):
Documentation: clarify %(contents:XXXX) doc
ref-filter: add support for %(contents:size)
Documentation/git-for-each-ref.txt | 27 +++++++++++++++++++++------
ref-filter.c | 7 ++++++-
t/t6300-for-each-ref.sh | 17 +++++++++++++++++
3 files changed, 44 insertions(+), 7 deletions(-)
--
2.27.0.221.ga08a83db2b.dirty
next reply other threads:[~2020-07-02 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 14:08 Christian Couder [this message]
2020-07-02 14:08 ` [PATCH v2 1/2] Documentation: clarify %(contents:XXXX) doc Christian Couder
2020-07-06 21:34 ` Junio C Hamano
2020-07-02 14:08 ` [PATCH v2 2/2] ref-filter: add support for %(contents:size) Christian Couder
2020-07-06 21:44 ` Junio C Hamano
2020-07-07 8:40 ` Christian Couder
2020-07-07 15:28 ` Junio C Hamano
2020-07-07 5:02 ` [PATCH v2 0/2] Add support for %(contents:size) in ref-filter Jeff King
2020-07-07 6:19 ` Christian Couder
2020-07-08 4:43 ` Jeff King
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=20200702140845.24945-1-chriscool@tuxfamily.org \
--to=christian.couder@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).