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

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

From
Derrick Stolee <stolee@gmail.com>
Date
Sep 17, 2018, 18:35 UTC
Message-ID
<43e8d5aa-5418-2e2d-2097-9e21e7a74825@gmail.com>
In-Reply-To
<xmqqy3c3agkr.fsf@gitster-ct.c.googlers.com>
On 9/14/2018 5:56 PM, Junio C Hamano wrote:
Show 10 quoted lines
> * ds/format-commit-graph-docs (2018-08-21) 2 commits
>   - commit-graph.txt: improve formatting for asciidoc
>   - Docs: Add commit-graph tech docs to Makefile
>
>   Design docs for the commit-graph machinery is now made into HTML as
>   well as text.
>
>   Will discard.
>   I am inclined to drop these, as I do not see much clarity in HTML
>   output over the text source.  Opinions?

Discarding is fine. I originally created it because I thought we were supposed to mark all documents for HTML generation. You're right, the HTML doesn't add anything.

Show 17 quoted lines
> * ds/commit-graph-with-grafts (2018-08-21) 8 commits
>   - commit-graph: close_commit_graph before shallow walk
>   - commit-graph: not compatible with uninitialized repo
>   - commit-graph: not compatible with grafts
>   - commit-graph: not compatible with replace objects
>   - test-repository: properly init repo
>   - commit-graph: update design document
>   - refs.c: upgrade for_each_replace_ref to be a each_repo_ref_fn callback
>   - refs.c: migrate internal ref iteration to pass thru repository argument
>
>   The recently introduced commit-graph auxiliary data is incompatible
>   with mechanisms such as replace & grafts that "breaks" immutable
>   nature of the object reference relationship.  Disable optimizations
>   based on its use (and updating existing commit-graph) when these
>   incompatible features are in use in the repository.
>
>   Replaced with a newer version.

I think this has been the same note for a few weeks now. What does it mean? Did I send a new version out that you haven't picked up?

Also, my "git log --topo-order" series was never picked up, but I see it has conflicts with 'next' now, so I'll rebase to resolve conflicts and send a v2.

Thanks, -Stolee

Previous: Junio C HamanoNext: Junio C Hamano
Message 12 of 17 in “What's cooking in git.git (Sep 2018, #03; Fri, 14)”
  1. Junio C HamanoSep 14, 2018
  2. Antonio OspiteSep 15, 2018
  3. Junio C HamanoSep 17, 2018
  4. Duy NguyenSep 16, 2018
  5. Ævar Arnfjörð BjarmasonSep 16, 2018
  6. Jeff KingSep 17, 2018
  7. Junio C HamanoSep 17, 2018
  8. Jeff KingSep 17, 2018
  9. Jonathan NiederSep 17, 2018
  10. brian m. carlsonSep 16, 2018
  11. Junio C HamanoSep 17, 2018
  12. Derrick StoleeSep 17, 2018
  13. Junio C HamanoSep 17, 2018
  14. Junio C HamanoSep 17, 2018
  15. pack-objects: handle island check for "external" delta baseJeff King, Sep 19, 2018
  16. Martin ÅgrenSep 19, 2018
  17. Jeff KingSep 19, 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.