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 (Jun 2019, #07; Fri, 28)
Date: Mon, 01 Jul 2019 09:05:39 -0700 [thread overview]
Message-ID: <xmqqr2797nak.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190701152215.GA43911@TaylorsMBP5815.attlocal.net> (Taylor Blau's message of "Mon, 1 Jul 2019 10:22:15 -0500")
Taylor Blau <me@ttaylorr.com> writes:
> Hi Junio,
>
> On Fri, Jun 28, 2019 at 03:17:42PM -0700, Junio C Hamano wrote:
>> * tb/ref-filter-multiple-patterns (2019-06-27) 1 commit
>> - ref-filter.c: find disjoint pattern prefixes
>>
>> "git for-each-ref" with multiple patterns have been optimized.
>>
>> Will merge to 'next'.
>
> Thanks for queueing this patch. For what it's worth, we have had this
> patch in GitHub's fork for the past month (?) or so, and it has been
> running without issue.
Thank you for working on this. It does look like a good thing to
do.
next prev parent reply other threads:[~2019-07-01 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 22:17 What's cooking in git.git (Jun 2019, #07; Fri, 28) Junio C Hamano
2019-07-01 13:16 ` ab/no-kwset, was " Johannes Schindelin
2019-07-01 16:39 ` Junio C Hamano
2019-07-01 21:22 ` Ævar Arnfjörð Bjarmason
2019-07-02 12:15 ` Johannes Schindelin
2019-07-01 15:02 ` Rohit Ashiwal
2019-07-01 16:05 ` Junio C Hamano
2019-07-01 15:22 ` Taylor Blau
2019-07-01 16:05 ` Junio C Hamano [this message]
2019-07-01 15:36 ` Taylor Blau
2019-07-02 20:44 ` Junio C Hamano
2019-07-03 11:13 ` Johannes Schindelin
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=xmqqr2797nak.fsf@gitster-ct.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).