list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Garima Singh <>
To: Junio C Hamano <>,
Subject: Re: What's cooking in git.git (Feb 2020, #02; Mon, 10)
Date: Tue, 11 Feb 2020 15:04:21 -0500
Message-ID: <> (raw)
In-Reply-To: <>

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 

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? 

Garima Singh

  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 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone