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

Re: Discussion: Future-Proofing Git for Massive AI Parallelism

From
TDtanish desai <tanishdesai37@icloud.com>
Date
Aug 8, 2025, 09:21 UTC
Message-ID
<5309CDB2-8254-440A-BE22-778CD9B10009@icloud.com>
In-Reply-To
<DB7PR02MB42658E4F3245CF0BA5B69AE4B326A@DB7PR02MB4265.eurprd02.prod.outlook.com>

Yes, this approach can help resolve merge conflicts, but a major issue still remains: while resolving these conflicts, the LLM often removes parts of the program's functionality or unintentionally introduces bugs. If we want to scale this system, we need a mechanism to run test cases from both branches being merged, so we can be confident that no functionality is lost during the merge and that the code remains stable.

> On 2 Aug 2025, at 3:08 AM, Skybuck Flying <skybuck2000@hotmail.com> wrote:
> 
> The AI/Gemini in general seems good at resolving/manipulating source code bases/files, so it should be able to solve merge conflicts, the question remains how big of a merge conflict it can truely solve before becoming confused and human intervention might be necessary, but by that point it might be too big of a mess for a human as well, so far the AI seems to be doing ok, but to early to tell.
Previous: Skybuck FlyingNext: tanish desai
Message 5 of 9 in “Discussion: Future-Proofing Git for Massive AI Parallelism”
  1. Skybuck FlyingJul 20, 2025
  2. Tanish Desai #TDJul 29, 2025
  3. Skybuck FlyingAug 1, 2025
  4. Skybuck FlyingAug 1, 2025
  5. tanish desaiAug 8, 2025
  6. tanish desaiAug 8, 2025
  7. tanish desaiAug 8, 2025
  8. Skybuck FlyingAug 14, 2025
  9. tanish desaiAug 18, 2025

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.