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

ds/generation-numbers (was Re: What's cooking in git.git (Jun 2018, #01; Fri, 1))

From
Derrick Stolee <stolee@gmail.com>
Date
Jun 1, 2018, 11:39 UTC
Message-ID
<4a7c6695-52cf-46a1-5a21-bf2e03a85f6b@gmail.com>
In-Reply-To
<xmqqa7sf7yzs.fsf@gitster-ct.c.googlers.com>
On 6/1/2018 3:21 AM, Junio C Hamano wrote:
Show 31 quoted lines
>
> * ds/commit-graph-lockfile-fix (2018-05-22) 1 commit
>    (merged to 'next' on 2018-05-24 at 3d12a02b0c)
>   + commit-graph: fix UX issue when .lock file exists
>   (this branch is used by ds/commit-graph-fsck; uses ds/generation-numbers.)
>
>   Update to ds/generation-numbers topic.
>
>   Wait for ds/generation-numbers
>
>
> * ds/generation-numbers (2018-05-22) 11 commits
>    (merged to 'next' on 2018-05-24 at 56fc38a1b6)
>   + commit-graph.txt: update design document
>   + merge: check config before loading commits
>   + commit: use generation number in remove_redundant()
>   + commit: add short-circuit to paint_down_to_common()
>   + commit: use generation numbers for in_merge_bases()
>   + ref-filter: use generation number for --contains
>   + commit-graph: always load commit-graph information
>   + commit: use generations in paint_down_to_common()
>   + commit-graph: compute generation numbers
>   + commit: add generation number to struct commit
>   + ref-filter: fix outdated comment on in_commit_list
>   (this branch is used by ds/commit-graph-fsck and ds/commit-graph-lockfile-fix.)
>
>   A recently added "commit-graph" datafile has learned to store
>   pre-computed generation numbers to speed up the decisions to stop
>   history traversal.
>
>   Will cook in 'next'.
On Wednesday, these were marked as "Will merge to 'master'" What changed?

Thanks, -Stolee

Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 5 in “What's cooking in git.git (Jun 2018, #01; Fri, 1)”
  1. Junio C HamanoJun 1, 2018
  2. ds/generation-numbers (was Re: What's cooking in git.git (Jun 2018, #01; Fri, 1))Derrick Stolee, Jun 1, 2018
  3. Junio C HamanoJun 1, 2018
  4. Derrick StoleeJun 2, 2018
  5. Stefan BellerJun 1, 2018

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.