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

Re: What's cooking in git.git (Mar 2020, #01; Tue, 3)

From
Taylor Blau <me@ttaylorr.com>
Date
Mar 3, 2020, 23:05 UTC
Message-ID
<20200303230554.GA11837@syl.local>
In-Reply-To
<xmqqimjl6pvn.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Tue, Mar 03, 2020 at 02:21:48PM -0800, Junio C Hamano wrote:
Show 11 quoted lines
> * tb/commit-graph-split-merge (2020-02-12) 3 commits
>  - builtin/commit-graph.c: support '--input=none'
>  - builtin/commit-graph.c: introduce '--input=<source>'
>  - builtin/commit-graph.c: support '--split[=<strategy>]'
>
>  The code to write out the commit-graph has been taught a few
>  options to control if the resulting graph chains should be merged
>  or a single new incremental graph is created.
>
>  Waiting for the discussion to settle.
>  cf. <20200212205028.GE4364@syl.local>

I think that this may be as settled as this discussion is going to reasonably get. I noticed that this has been on the "What's Cooking" as waiting for the discussion to cool down, but there haven't been any new messages.

I think that the options are probably unlikely to change in the future, and unless there are some serious reservations that nobody has raised, that we should go forward with the patches as they are.

What's in 'v3' of that series [1] is ready to merge, in my opinion.

Thanks, Taylor

[1]: https://lore.kernel.org/git/cover.1581486293.git.me@ttaylorr.com/#t
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 15 in “What's cooking in git.git (Mar 2020, #01; Tue, 3)”
  1. Junio C HamanoMar 3, 2020
  2. Taylor BlauMar 3, 2020
  3. Junio C HamanoMar 3, 2020
  4. Junio C HamanoMar 3, 2020
  5. Taylor BlauMar 3, 2020
  6. Heba WalyMar 4, 2020
  7. Jonathan TanMar 4, 2020
  8. Junio C HamanoMar 4, 2020
  9. Heba WalyMar 5, 2020
  10. update how-to-maintain-gitJunio C Hamano, Mar 6, 2020
  11. Eric SunshineMar 6, 2020
  12. Junio C HamanoMar 6, 2020
  13. Martin ÅgrenMar 7, 2020
  14. hv/receive-denycurrent-everywhere, was Re: What's cooking in git.git (Mar 2020, #01; Tue, 3)Johannes Schindelin, Mar 4, 2020
  15. Junio C HamanoMar 4, 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.