From: Junio C Hamano <firstname.lastname@example.org>
To: Matthew DeVore <email@example.com>
Cc: firstname.lastname@example.org, Johannes.Schindelin@gmx.de
Subject: Re: What's cooking in git.git (Aug 2019, #03; Tue, 6)
Date: Thu, 08 Aug 2019 12:03:45 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <20190808182242.GA96790@comcast.net> (Matthew DeVore's message of "Thu, 8 Aug 2019 11:22:42 -0700")
Matthew DeVore <firstname.lastname@example.org> writes:
> 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 doubt it will be during -rc freeze period, before the final week
of the upcoming release.
> 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?
That may be some of it. When we approach -rc (that was a few weeks
ago), any large change not ready for 'next' would get backburnered
to allow higher priority "oops, that one is already in or just about
to go in 'master', but it needs this fixup before the final" topics
to graduate sooner.
prev parent reply other threads:[~2019-08-08 19:03 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
2019-08-08 19:03 ` Junio C Hamano [this message]
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:
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 \
* 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
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).