git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] commit-graph: add verify changed paths option

From
Taylor Blau <me@ttaylorr.com>
Date
Jul 31, 2020, 18:06 UTC
Message-ID
<20200731180636.GA59489@syl.lan>
In-Reply-To
<xmqqh7tn4neo.fsf@gitster.c.googlers.com>
On Fri, Jul 31, 2020 at 10:14:39AM -0700, Junio C Hamano wrote:
Show 15 quoted lines
> "Son Luong Ngoc via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > From: Son Luong Ngoc <sluongng@gmail.com>
> >
> > Add '--has-changed-paths' option to 'git commit-graph verify' subcommand
> > to validate whether the commit-graph was written with '--changed-paths'
> > option.
>
> The implementation seems to be only about "does this section exist?"
> and not "does this section have healthy/uncorrupted data?", which
> feels a bit strange for "verify".  Instead of setting ourselves up
> to having to add "--has-this-section" and "--has-that-section" every
> time a new kind of data is added to the system, how about giving the
> verify command an option to list all the sections found in the file,
> or a separate "git commit-graph list-sections" subcommand?

Completely agreed. When I suggested that Son work on this, I more had in mind something like 'git commit-graph verify --changed-paths' to mean "verify the integrity of the commit-graph(s), including regenerating changed-path Bloom filters and making sure they match".

If you are just curious whether or not the section exists, I'd rather write a script to look for the 'BIDX' or 'BDAT' chunk IDs. That said, if they're spread across incremental, maybe it makes more sense to extend the commit-graph test tool.

I dunno.

Thanks, Taylor

Previous: Junio C HamanoNext: Jeff King
Message 4 of 8 in “commit-graph: add verify changed paths option”
  1. commit-graph: add verify changed paths optionSon Luong Ngoc via GitGitGadget, Jul 31, 2020
  2. Christian CouderJul 31, 2020
  3. Junio C HamanoJul 31, 2020
  4. Taylor BlauJul 31, 2020
  5. Jeff KingJul 31, 2020
  6. Taylor BlauJul 31, 2020
  7. Jeff KingJul 31, 2020
  8. Son Luong NgocJul 31, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.