From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Taylor Blau <me@ttaylorr.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2020, #04; Thu, 30)
Date: Mon, 4 May 2020 18:16:38 -0600 [thread overview]
Message-ID: <20200505001638.GB64230@syl.local> (raw)
In-Reply-To: <xmqq4ksvitcd.fsf@gitster.c.googlers.com>
On Mon, May 04, 2020 at 08:59:46AM -0700, Junio C Hamano wrote:
> Taylor Blau <me@ttaylorr.com> writes:
>
> > On Fri, May 01, 2020 at 02:24:11PM -0600, Taylor Blau wrote:
> >> One thing that may have been passed over is my series to teach the
> >> bitmap machinery how to quickly interpret '--filter=tree:0' by
> >> discarding non-named trees from the result set. That is here:
> >>
> >> https://lore.kernel.org/git/cover.1587597151.git.me@ttaylorr.com/
> >>
> >> This didn't get much review outside of from Peff, who wrote some of the
> >> patches, so I'd be happy to re-send it or wait longer for others to have
> >> a look, too. For what it's worth, these changes are fairly
> >> straightforward and we have been running them at GitHub (and allowing
> >> partial clones with `--filter=tree:0`!) for some time now.
> >
> > At the risk of nagging, would you like this one to be re-sent, or are
> > you feeling OK about picking it up?
>
> Ah, I completely missed this message. I have no strong opinions on
> the topic itself myself and I do not remember seeing anything
> objectionable in the implementation, but a resend may give it the
> last chance for exposure.
No worries; thanks for clarifying. I resent it without changes as [1].
> Thanks.
Thanks,
Taylor
[1]: https://lore.kernel.org/git/cover.1588633810.git.me@ttaylorr.com/
prev parent reply other threads:[~2020-05-05 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 23:04 What's cooking in git.git (Apr 2020, #04; Thu, 30) Junio C Hamano
2020-05-01 20:24 ` Taylor Blau
2020-05-01 20:55 ` Junio C Hamano
2020-05-01 22:40 ` Taylor Blau
2020-05-04 15:59 ` Junio C Hamano
2020-05-05 0:16 ` Taylor Blau [this message]
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=20200505001638.GB64230@syl.local \
--to=me@ttaylorr.com \
--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).