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

Re: What's cooking in git.git (Aug 2023, #01; Wed, 2)

From
Elijah Newren <newren@gmail.com>
Date
Aug 7, 2023, 16:56 UTC
Message-ID
<CABPp-BE5h6C1iuGDz4HdJzb2bDLidEnQ0_U4fv93JrYXA2_cbw@mail.gmail.com>
In-Reply-To
<xmqqv8dqhlkz.fsf@gitster.g>
On Mon, Aug 7, 2023 at 9:19 AM Junio C Hamano <gitster@pobox.com> wrote:
>
[...]
Show 9 quoted lines
> >> However in a recent article
> >> (https://github.blog/2023-07-27-scaling-merge-ort-across-github/)
> >> GitHub says that they are already using git-replay (though not sure
> >> it's this exact version or another one), and GitLab plans to use it
> >> too.
>
> So there are plenty folks who are capable of reviewing but they are
> not interested in giving it to the general public by withholding
> their reviews ;-)?

I can see how one could jump to that conclusion, but I don't think it's warranted. I have a little information that might shed some light:

-----

At the beginning of July, well before the above link came out, Johannes sent me an email pointing me at https://github.blog/changelog/2023-06-28-rebase-commits-now-created-using-the-merge-ort-strategy/. In the email, he also noted my earlier stated concerns on the list (about releasing `replay` early possibly painting us into a corner preventing some desired goals for the tool from being realized), and tried to ensure we could still work towards having a `replay` command like the one I envisioned while also asking for my thoughts on pushing for the current portion of work to be published and included in git. My sense was he was pushing for the work to be released, but just being careful about my concerns first.

Unfortunately, I was on vacation that week, and sadly have otherwise been buried in coming up to speed on a new team and haven't had time to even respond to git-related stuff. I didn't respond to him until late last week.

I pointed out that the 'EXPERIMENTAL' banner addresses most of my concerns so it should be fine to move forward, but I suspect my delay has resulted in him now being buried in other matters, and in the mean-time the article Christian highlighted was produced by others.

-----

Anyway, hope that helps. I did review V2 and have been meaning to comment on V3 (and respond to Toon's comments), though not sure my "review" counts as such since I'm the original author of most of the patches...

(And sorry for being missing in action. I've flagged a few other emails that I'm hoping I can follow up on, but my time is currently quite limited...)

Previous: Taylor BlauNext: Johannes Schindelin
Message 14 of 15 in “What's cooking in git.git (Aug 2023, #01; Wed, 2)”
  1. Junio C HamanoAug 2, 2023
  2. jt/path-filter-fix (was: Re: What's cooking in git.git (Aug 2023, #01; Wed, 2))Taylor Blau, Aug 2, 2023
  3. Junio C HamanoAug 2, 2023
  4. Taylor BlauAug 2, 2023
  5. Rubén JustoAug 7, 2023
  6. leak in jt/path-filter-fix, was Re: What's cooking in git.git (Aug 2023, #01; Wed, 2)Jeff King, Aug 8, 2023
  7. Jeff KingAug 8, 2023
  8. Taylor BlauAug 8, 2023
  9. Jeff KingAug 8, 2023
  10. Jonathan TanAug 11, 2023
  11. Christian CouderAug 7, 2023
  12. Junio C HamanoAug 7, 2023
  13. Taylor BlauAug 7, 2023
  14. Elijah NewrenAug 7, 2023
  15. Johannes SchindelinAug 17, 2023

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.