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

RFC -- making a plan for remainder of merge-ort

From
Elijah Newren <newren@gmail.com>
Date
Feb 2, 2021, 03:52 UTC
Message-ID
<CABPp-BHvk5RLq3OOYhcQZJ_9w6hbQUVurJiRrks8kcGq5-rn0g@mail.gmail.com>
Hi everyone,

There will be ~11 more series (with about ~6-7 patches per series) before merge-ort is complete. Now that gitster/en/merge-ort-perf has merged to next, I can start submitting the next series. Some questions before I do so, though:

* What's the right rate to submit them to not overwhelm reviewers? One
per week?  I didn't get much feedback on this for the past series.
[One per week, assuming the git-2.32 cycle is 3 months long, would
mean finishing in about 3 months, i.e. just a few weeks before
git-2.32-rc0.]
* My focus for the next few series is on diffcore-rename.c, which will
also affect things other than merge-ort.  While each series is
self-contained, given that 2.31-rc0 is just over 3 weeks away I'm
wondering if it makes sense to hold my future diffcore-rename series
out of 2.31 and start merging them in the 2.32 cycle.  Thoughts?

Thanks, Elijah

Next: Derrick Stolee
Message 1 of 3 in “RFC -- making a plan for remainder of merge-ort”
  1. Elijah NewrenFeb 2, 2021
  2. Derrick StoleeFeb 2, 2021
  3. Elijah NewrenFeb 3, 2021

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.