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 0/4] bisect--helper: fix reading many paths
Date: Sun, 29 Mar 2009 11:44:38 +0200 [thread overview]
Message-ID: <20090329114438.6642fb64.chriscool@tuxfamily.org> (raw)
These patches fix reading more than one path in "git bisect--helper":
quote: implement "sq_dequote_many" to unwrap many args in one string
quote: add "sq_dequote_to_argv" to put unwrapped args in an argv
array
bisect: fix reading more than one path in "$GIT_DIR/BISECT_NAMES"
bisect: test bisecting with paths
bisect.c | 14 +++++-----
quote.c | 35 +++++++++++++++++++++++-
quote.h | 10 +++++++
t/t6030-bisect-porcelain.sh | 60 +++++++++++++++++++++++++++++++++++++++++++
4 files changed, 110 insertions(+), 9 deletions(-)
reply other threads:[~2009-03-29 9:47 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=20090329114438.6642fb64.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).