From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2020, #04; Thu, 30)
Date: Fri, 1 May 2020 14:24:11 -0600 [thread overview]
Message-ID: <20200501202411.GA41612@syl.local> (raw)
In-Reply-To: <xmqqmu6spocm.fsf@gitster.c.googlers.com>
Hi Junio,
On Thu, Apr 30, 2020 at 04:04:25PM -0700, Junio C Hamano wrote:
Thanks for an update. Here are some new topics that I have been tracking
as well:
> [New Topics]
The only topics that I've been tracking that aren't here are still going
through some review. Those are:
* Sibi's patches to start building with CMake [1].
* The fifth part of Denton's patches to replace 'test_must_fail'
usage with another approach [2].
* Dogulas Fuller's patches to update a quoting issue in documentation
[3].
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.
Thanks,
Taylor
[1]: https://lore.kernel.org/git/pull.614.git.1587700897.gitgitgadget@gmail.com/
[2]: https://lore.kernel.org/git/cover.1588162842.git.liu.denton@gmail.com/
[3]: https://lore.kernel.org/git/63f35287c9ced4d674f938bedd439aefa6c46f41.camel@gmail.com/
next prev parent reply other threads:[~2020-05-01 20:24 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 [this message]
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
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=20200501202411.GA41612@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.
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).