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

Re: merge-recur status

From
Junio C Hamano <junkio@cox.net>
Date
Aug 10, 2006, 08:03 UTC
Message-ID
<7vwt9hvwzb.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0608100949250.13885@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> P.S.: Pavel, thanks for the "A dedicated programmer with good C and Python 
> skills could rewrite git-merge-recursive.py in C in 2 days, I believe. Add 
> a few days of bug fixing, of course." underestimation. I do not know if I 
> had started fiddling with it if I had known how involved it is.

It indeed _is_ involved, and not just C vs Python but the latter being able to rely on multiple processes without worrying about state clean-ups.

I am quite impressed by and happy with the merge-recur work.
Previous: Johannes Schindelin
Message 5 of 5 in “merge-recur status”
  1. Johannes SchindelinAug 9, 2006
  2. Junio C HamanoAug 9, 2006
  3. Fredrik KuivinenAug 10, 2006
  4. Johannes SchindelinAug 10, 2006
  5. Junio C HamanoAug 10, 2006

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.