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

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

From
Christian Couder <chriscool@tuxfamily.org>
Date
May 17, 2009, 16:35 UTC
Message-ID
<200905171835.41213.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".

To do that it introduces an "unparse_commit" function that may be usefull in other cases, for example see:

http://article.gmane.org/gmane.comp.version-control.git/114916
Ps: sorry to send this cover letter late because of a bug in the
script I used to send the series.
  bisect: rework some rev related functions to make them more reusable
  commit: add function to unparse a commit and its parents
  bisect: check ancestors without forking a "git rev-list" process
 bisect.c                    |   79 
+++++++++++++++++++-----------------------
 commit.c                    |   20 +++++++++++
 commit.h                    |    2 +
 t/t6030-bisect-porcelain.sh |   13 +------
 4 files changed, 59 insertions(+), 55 deletions(-)
Message 1 of 1 in “Avoid forking a process when checking merge bases”
  1. 0/3 Avoid forking a process when checking merge basesChristian Couder, May 17, 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.