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 (May 2020, #02; Tue, 5)
Date: Wed, 6 May 2020 11:18:11 -0600 [thread overview]
Message-ID: <20200506171811.GA6078@syl.local> (raw)
In-Reply-To: <xmqq8si69fda.fsf@gitster.c.googlers.com>
Hi Junio,
Thanks for an update. I couldn't find anything in my list of active
topics that you're not already tracking below, so I'll just respond to
the topics I authored:
On Tue, May 05, 2020 at 03:38:41PM -0700, Junio C Hamano wrote:
> * tb/bitmap-walk-with-tree-zero-filter (2020-05-04) 4 commits
> - pack-bitmap: pass object filter to fill-in traversal
> - pack-bitmap.c: support 'tree:0' filtering
> - pack-bitmap.c: make object filtering functions generic
> - list-objects-filter: treat NULL filter_options as "disabled"
>
> The object walk with object filter "--filter=tree:0" can now take
> advantage of the pack bitmap when available.
>
> Will merge to 'next'.
Thanks very much!
> * tb/commit-graph-no-check-oids (2020-05-04) 8 commits
> - commit-graph: drop COMMIT_GRAPH_WRITE_CHECK_OIDS flag
> - t5318: reorder test below 'graph_read_expect'
> - commit-graph.c: simplify 'fill_oids_from_commits'
> - builtin/commit-graph.c: dereference tags in builtin
> - builtin/commit-graph.c: extract 'read_one_commit()'
> - commit-graph.c: peel refs in 'add_ref_to_set'
> - commit-graph.c: show progress of finding reachable commits
> - commit-graph.c: extract 'refs_cb_data'
>
> Clean-up the commit-graph codepath.
>
> Expecting a reroll
> cf. <20200505161649.GG69300@syl.local>
Sent: https://lore.kernel.org/git/cover.1588723543.git.me@ttaylorr.com/.
Thanks,
Taylor
prev parent reply other threads:[~2020-05-06 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 22:38 What's cooking in git.git (May 2020, #02; Tue, 5) Junio C Hamano
2020-05-05 22:53 ` Carlo Marcelo Arenas Belón
2020-05-05 23:06 ` Junio C Hamano
2020-05-06 17:18 ` 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=20200506171811.GA6078@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.