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

Re: [RFC] custom strategies in builtin-merge

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 26, 2008, 02:37 UTC
Message-ID
<alpine.DEB.1.00.0807260435470.11976@eeepc-johanness>
In-Reply-To
<7vvdyto3da.fsf@gitster.siamese.dyndns.org>
Hi,
On Fri, 25 Jul 2008, Junio C Hamano wrote:
Show 9 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > ... especially since I hope that we have them builtin soon, and not 
> > only that, but have builtin-merge call them as C functions, not with 
> > fork() and exec().
> 
> Because builtin-merge.c does not directly use fork/exec but uses 
> run_command() interface, non POSIX platforms can spawn subprocesses just 
> fine, can't they?
Yes, they can.  Slowly, but they do.

But why should they? Efficient merging is such a prominent feature of Git; I do not agree to let it remain a second-class feature.

Ciao, Dscho

Previous: Junio C Hamano
Message 6 of 6 in “[RFC] custom strategies in builtin-merge”
  1. Miklos VajnaJul 25, 2008
  2. Sverre RabbelierJul 25, 2008
  3. Junio C HamanoJul 26, 2008
  4. Johannes SchindelinJul 26, 2008
  5. Junio C HamanoJul 26, 2008
  6. Johannes SchindelinJul 26, 2008

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.