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

Re: What's cooking in git.git (Oct 2020, #02; Fri, 9)

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 9, 2020, 16:28 UTC
Message-ID
<xmqqpn5rtld1.fsf@gitster.c.googlers.com>
In-Reply-To
<512a3dc5-4937-8679-c4c8-5144ac50450b@gmail.com>
Derrick Stolee <stolee@gmail.com> writes:
> As for discarding them all: we would need to add code to "reparse"
> a commit from the object database. Perhaps that is doable, but we
> have so far not removed data from a parsed 'struct commit'. This
> is probably the easiest way forward to guarantee correct data here.

Oh, no, by "discarding" I just meant to blow away suspect on-disk files and recompute them from scratch. I didn't have anything clever like correcting in-core data structure by parsing the commits and updating.

> Again, let's find a way to test this before committing.
Yes, that is sensible.  After all this is not a recent regression.
Previous: Derrick StoleeNext: Derrick Stolee
Message 3 of 4 in “What's cooking in git.git (Oct 2020, #02; Fri, 9)”
  1. Junio C HamanoOct 9, 2020
  2. Derrick StoleeOct 9, 2020
  3. Junio C HamanoOct 9, 2020
  4. Derrick StoleeOct 9, 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.