From: Matthew DeVore <matvore@comcast.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes.Schindelin@gmx.de
Subject: Re: What's cooking in git.git (Aug 2019, #03; Tue, 6)
Date: Thu, 8 Aug 2019 11:22:42 -0700 [thread overview]
Message-ID: <20190808182242.GA96790@comcast.net> (raw)
In-Reply-To: <xmqqv9vahs6p.fsf@gitster-ct.c.googlers.com>
On Tue, Aug 06, 2019 at 02:58:38PM -0700, Junio C Hamano wrote:
>
> * md/list-objects-filter-combo (2019-06-28) 10 commits
> - list-objects-filter-options: make parser void
> - list-objects-filter-options: clean up use of ALLOC_GROW
> - list-objects-filter-options: allow mult. --filter
> - strbuf: give URL-encoding API a char predicate fn
> - list-objects-filter-options: make filter_spec a string_list
> - list-objects-filter-options: move error check up
> - list-objects-filter: implement composite filters
> - list-objects-filter-options: always supply *errbuf
> - list-objects-filter: put omits set in filter struct
> - list-objects-filter: encapsulate filter components
>
> The list-objects-filter API (used to create a sparse/lazy clone)
> learned to take a combined filter specification.
>
> Will merge to 'next'.
>
This has been the status for a while, and I don't see it on "next."
I notice Johannes wanted a fix for incorrect strbuf usage to fix a linter check
- (just saw his earlier message now) is that the cause of the delay?
next prev parent reply other threads:[~2019-08-08 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 21:58 What's cooking in git.git (Aug 2019, #03; Tue, 6) Junio C Hamano
2019-08-07 1:05 ` Rohit Ashiwal
2019-08-07 5:14 ` Junio C Hamano
2019-08-08 18:22 ` Matthew DeVore [this message]
2019-08-08 19:03 ` 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=20190808182242.GA96790@comcast.net \
--to=matvore@comcast.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).