From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2020, #04; Thu, 30)
Date: Mon, 04 May 2020 08:59:46 -0700 [thread overview]
Message-ID: <xmqq4ksvitcd.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200501224004.GA45288@syl.local> (Taylor Blau's message of "Fri, 1 May 2020 16:40:04 -0600")
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.
Thanks.
next prev parent reply other threads:[~2020-05-04 15:59 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 [this message]
2020-05-05 0:16 ` Taylor Blau
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=xmqq4ksvitcd.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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).