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

[StGIT PATCH 0/6] David's conflict series using my subprocess stuff

From
Karl Hasselström <kha@treskal.com>
Date
Aug 26, 2007, 20:42 UTC
Message-ID
<20070826203745.16700.5655.stgit@yoghurt>

This is David's conflict series, rebased on top of my subprocess calling series. There was one place where it used to have to call popen2.Popen3 directly, since none of our existing ten subprocess functions could do that particular job. But the new subprocess machinery can. (This was the original motivation for that refactoring, by the way.)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Next: Karl Hasselström
Message 1 of 7 in “David's conflict series using my subprocess stuff”
  1. 0/6 David's conflict series using my subprocess stuffKarl Hasselström, Aug 26, 2007
  2. 1/6 Split git.merge into two functionsKarl Hasselström, Aug 26, 2007
  3. 2/6 Leave working dir and index alone after failed (conflicting) pushKarl Hasselström, Aug 26, 2007
  4. 3/6 Added a test case to check what happens when push finds a conflictKarl Hasselström, Aug 26, 2007
  5. 4/6 Simplify merge_recursiveKarl Hasselström, Aug 26, 2007
  6. 5/6 Use the output from merge-recursive to list conflictsKarl Hasselström, Aug 26, 2007
  7. 6/6 Better error message if merge failsKarl Hasselström, Aug 26, 2007

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.