From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH v2 0/2] Avoid forking a process when checking merge bases
Date: Wed, 27 May 2009 07:09:40 +0200 [thread overview]
Message-ID: <20090527050656.3694.86787.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".
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 reply other threads:[~2009-05-27 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 5:09 Christian Couder [this message]
2009-05-27 5:09 ` [PATCH v2 1/2] bisect: rework some rev related functions to make them more reusable Christian Couder
2009-05-27 5:09 ` [PATCH v2 2/2] bisect: check ancestors without forking a "git rev-list" process Christian Couder
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=20090527050656.3694.86787.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).