From: Matthew DeVore <matvore@comcast.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2019, #06; Wed, 26)
Date: Thu, 27 Jun 2019 12:48:09 -0700 [thread overview]
Message-ID: <20190627194809.GA54617@comcast.net> (raw)
In-Reply-To: <xmqq36jwc75i.fsf@gitster-ct.c.googlers.com>
On Wed, Jun 26, 2019 at 03:29:29PM -0700, Junio C Hamano wrote:
> * md/list-objects-filter-combo (2019-06-17) 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: make API easier to use
>
> The list-objects-filter API (used to create a sparse/lazy clone)
> learned to take a combined filter specification.
>
> Will merge to 'next'.
>
Great, thank you. I do want to apply jonathantanmy@google.com's
readability/textual suggestions. Can you wait until the next roll-up before
merging, please? I'll send it out today.
next prev parent reply other threads:[~2019-06-27 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 22:29 What's cooking in git.git (Jun 2019, #06; Wed, 26) Junio C Hamano
2019-06-26 22:41 ` Jonathan Tan
2019-06-27 17:11 ` Junio C Hamano
2019-06-27 19:48 ` Matthew DeVore [this message]
2019-06-28 2:26 ` Junio C Hamano
2019-06-28 6:24 ` Jeff King
2019-07-01 14:07 ` Barret Rhoden
2019-07-01 16:29 ` Junio C Hamano
2019-07-01 17:55 ` Barret Rhoden
2019-06-28 19:11 ` Thomas Gummerer
2019-06-29 14:08 ` Phillip Wood
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190627194809.GA54617@comcast.net \
--to=matvore@comcast.net \
--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.
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 NNTP newsgroup(s).