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

[PATCH v2 0/2] Avoid forking a process when checking merge bases

From
Christian Couder <chriscool@tuxfamily.org>
Date
May 27, 2009, 05:09 UTC
Message-ID
<20090527050656.3694.86787.chriscool@tuxfamily.org>

The goal of this patch series is to check if good revisions are ancestor of the bad revision without forking a process to launch "git rev-list $good ^$bad".

This new version of this patch series does not use an "unparse_commit" function anymore, we use "clear_commit_marks" instead.

  bisect: rework some rev related functions to make them more reusable
  bisect: check ancestors without forking a "git rev-list" process
 bisect.c                    |   79 +++++++++++++++++++-----------------------
 t/t6030-bisect-porcelain.sh |   13 +------
 2 files changed, 37 insertions(+), 55 deletions(-)
Next: Christian Couder
Message 1 of 3 in “Avoid forking a process when checking merge bases”
  1. 0/2 Avoid forking a process when checking merge basesChristian Couder, May 27, 2009
  2. 1/2 bisect: rework some rev related functions to make them more reusableChristian Couder, May 27, 2009
  3. 2/2 bisect: check ancestors without forking a "git rev-list" processChristian Couder, May 27, 2009

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.