From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/3] Avoid forking a process when checking merge bases
Date: Sun, 17 May 2009 18:35:41 +0200 [thread overview]
Message-ID: <200905171835.41213.chriscool@tuxfamily.org> (raw)
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(-)
reply other threads:[~2009-05-17 16:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905171835.41213.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).