From: Garima Singh <garimasigit@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2020, #02; Mon, 10)
Date: Tue, 11 Feb 2020 15:04:21 -0500 [thread overview]
Message-ID: <819852c9-68dc-11e3-d81d-ddd216953d72@gmail.com> (raw)
In-Reply-To: <xmqqimkexeed.fsf@gitster-ct.c.googlers.com>
On 2/10/2020 5:31 PM, Junio C Hamano wrote:
> * gs/commit-graph-path-filter (2020-02-06) 11 commits
> - commit-graph: add GIT_TEST_COMMIT_GRAPH_CHANGED_PATHS test flag
> - revision.c: use Bloom filters to speed up path based revision walks
> - commit-graph: add --changed-paths option to write subcommand
> - commit-graph: reuse existing Bloom filters during write.
> - commit-graph: write Bloom filters to commit graph file
> - commit-graph: examine commits by generation number
> - commit-graph: examine changed-path objects in pack order
> - commit-graph: compute Bloom filters for changed paths
> - diff: halt tree-diff early after max_changes
> - bloom: core Bloom filter implementation for changed paths
> - commit-graph: use MAX_NUM_CHUNKS
>
> Introduce an extension to the commit-graph to make it efficient to
> check for the paths that were modified at each commit using Bloom
> filters.
>
> Breakage due to byte-order dependency reported.
>
Hey Junio!
We fixed the byte-order dependency bug in the patch I just sent out
here:
https://lore.kernel.org/git/ba856e20-0a3c-e2d2-6744-b9abfacdc465@gmail.com/
I am squashing this patch into the appropriate commits in v3, which I will
send out after people have had a chance to complete their review of v2.
Could you please apply that patch on top of the pu branch
gs/commit-graph-path-filter so that it also has the fix?
Cheers!
Garima Singh
next prev parent reply other threads:[~2020-02-11 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 22:31 What's cooking in git.git (Feb 2020, #02; Mon, 10) Junio C Hamano
2020-02-11 15:03 ` ds/ (was Re: What's cooking in git.git (Feb 2020, #02; Mon, 10)) Derrick Stolee
2020-02-11 20:04 ` Garima Singh [this message]
2020-02-11 20:56 ` What's cooking in git.git (Feb 2020, #02; Mon, 10) Junio C Hamano
2020-02-11 20:56 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2020-02-10 22:29 Junio C Hamano
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=819852c9-68dc-11e3-d81d-ddd216953d72@gmail.com \
--to=garimasigit@gmail.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).