git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 (Mar 2020, #10; Tue, 31)
Date: Thu, 2 Apr 2020 08:42:05 -0400	[thread overview]
Message-ID: <eb588d3b-eec4-b904-82ed-80b228387726@gmail.com> (raw)
In-Reply-To: <xmqq4ku46s8z.fsf@gitster.c.googlers.com>

On 3/31/2020 7:04 PM, Junio C Hamano wrote:
>
> --------------------------------------------------
> [Stalled]
> 
> * gs/commit-graph-path-filter (2020-03-30) 16 commits
>  - commit-graph: add GIT_TEST_COMMIT_GRAPH_CHANGED_PATHS test flag
>  - t4216: add end to end tests for git log with Bloom filters
>  - revision.c: add trace2 stats around Bloom filter usage
>  - 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
>  - diff: skip batch object download when possible
>  - 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.c: core Bloom filter implementation for changed paths.
>  - bloom.c: introduce core Bloom filter constructs
>  - bloom.c: add the murmur3 hash implementation
>  - commit-graph: define and 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.
> 
>  Expecting a reroll.
>  cf. <fdcbd793-57c2-f5ea-ccb9-cf34e911b669@gmail.com>
>  Breakage due to byte-order dependency reported.
> 

Hey Junio!

I sent out v3 of this series on the 29th of March. 

See: 
https://public-inbox.org/git/pull.497.v3.git.1585528298.gitgitgadget@gmail.com/T/#u
and
https://public-inbox.org/git/6b61fec4-3334-8bfc-d4b8-3921e35cf6a6@gmail.com/

The sequence of commits you have here is actually the updated version and I 
see it getting picked up in 'pu' as well. 
However, the series is still marked as 'Stalled'. 

Shouldn't this be in the 'Cooking' section with an updated description
now that it has been rerolled? 

Again, Thanks for the patience and letting this bake in pu. 

Hope you and everyone on here is staying safe and healthy in 
these trying times.

Cheers,
Garima Singh



  parent reply	other threads:[~2020-04-02 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 23:04 What's cooking in git.git (Mar 2020, #10; Tue, 31) Junio C Hamano
2020-04-02  6:56 ` Miriam R.
2020-04-02 17:42   ` Junio C Hamano
2020-04-02 12:42 ` Garima Singh [this message]
2020-04-02 17:40   ` Junio C Hamano
2020-04-02 16:10 ` Phillip Wood
2020-04-03 20:04 ` Taylor Blau
2020-04-03 22:13   ` Junio C Hamano
2020-04-03 22:56 ` Emily Shaffer

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=eb588d3b-eec4-b904-82ed-80b228387726@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).