From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, John Tapsell <johnflux@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: [PATCH v2 0/2] bisect--helper: string output variables together with "&&"
Date: Mon, 30 Mar 2009 06:59:45 +0200 [thread overview]
Message-ID: <20090330065945.edc862e3.chriscool@tuxfamily.org> (raw)
The goal of this 2 patches is to get rid of the need to pipe the
output of "eval 'git bisect--helper --next-vars'" into a "while read"
loop.
The only change since the previous version is that a brown paper bag bug
in "show_tried_revs" is fixed in the second patch.
rev-list: pass a flag as last argument of "show_bisect_vars"
bisect--helper: string output variables together with "&&"
bisect.c | 3 ++-
bisect.h | 9 +++++++--
builtin-rev-list.c | 42 +++++++++++++++++++++++++-----------------
git-bisect.sh | 15 +--------------
4 files changed, 35 insertions(+), 34 deletions(-)
reply other threads:[~2009-03-30 5:02 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=20090330065945.edc862e3.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johnflux@gmail.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).