From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Timo Hirvonen <tihirvon@gmail.com>, git@vger.kernel.org
Subject: [PATCH] bisect: quote pathnames for eval safety.
Date: Sun, 27 Nov 2005 17:51:23 -0800 [thread overview]
Message-ID: <7vmzjp35gk.fsf_-_@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0511271106360.13959@g5.osdl.org> (Linus Torvalds's message of "Sun, 27 Nov 2005 11:32:03 -0800 (PST)")
Linus Torvalds <torvalds@osdl.org> writes:
> Almost totally untested, and I guarantee that if your pathnames have
> spaces in them (or your GIT_DIR has spaces in it) this won't work. I don't
> know how to fix that, my shell programming isn't good enough.
Like this? I've placed the bisect patch with this in the
proposed updates.
---
git-bisect.sh | 16 ++++++++++++----
1 files changed, 12 insertions(+), 4 deletions(-)
applies-to: 7da44ab45773e0a424c1e08c838c1f6deeb6ceb2
82c8f5bed2ae61f1f368cfca84f6b0194b1ad208
diff --git a/git-bisect.sh b/git-bisect.sh
index 2455f00..d4196f9 100755
--- a/git-bisect.sh
+++ b/git-bisect.sh
@@ -1,9 +1,16 @@
#!/bin/sh
. git-sh-setup
+sq() {
+ for x
+ do
+ echo "$x" | sed -e "s/'/'\\\\''/g" -e "s/^/'/" -e "s/\$/'/"
+ done
+}
+
usage() {
echo >&2 'usage: git bisect [start|bad|good|next|reset|visualize]
-git bisect start reset bisect state and start bisection.
+git bisect start [<pathspec>] reset bisect state and start bisection.
git bisect bad [<rev>] mark <rev> a known-bad revision.
git bisect good [<rev>...] mark <rev>... known-good revisions.
git bisect next find next bisection to test and check it out.
@@ -56,8 +63,8 @@ bisect_start() {
rm -f "$GIT_DIR/refs/heads/bisect"
rm -rf "$GIT_DIR/refs/bisect/"
mkdir "$GIT_DIR/refs/bisect"
- echo "git-bisect start $@" >"$GIT_DIR/BISECT_LOG"
- echo "$@" > "$GIT_DIR/BISECT_NAMES"
+ sq git-bisect start "$@" >"$GIT_DIR/BISECT_LOG"
+ sq "$@" >"$GIT_DIR/BISECT_NAMES"
}
bisect_bad() {
@@ -142,7 +149,8 @@ bisect_next() {
bisect_visualize() {
bisect_next_check fail
- gitk bisect/bad --not `cd "$GIT_DIR/refs" && echo bisect/good-*` -- $(cat $GIT_DIR/BISECT_NAMES)
+ not=`cd "$GIT_DIR/refs" && echo bisect/good-*`
+ eval gitk bisect/bad --not $not -- $(cat "$GIT_DIR/BISECT_NAMES")
}
bisect_reset() {
---
0.99.9.GIT
next prev parent reply other threads:[~2005-11-28 1:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 1:15 [PATCH 0/4] Repository format version check series Junio C Hamano
2005-11-27 10:56 ` What's in master and pu (aka when will 1.0rc4 be out) Junio C Hamano
2005-11-27 13:11 ` Timo Hirvonen
2005-11-27 19:32 ` Linus Torvalds
2005-11-27 21:08 ` Junio C Hamano
2005-11-28 1:51 ` Junio C Hamano [this message]
2005-11-28 2:12 ` [PATCH] bisect: quote pathnames for eval safety Junio C Hamano
2005-11-29 6:42 ` [PATCH 0/4] Repository format version check series Martin Atukunda
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=7vmzjp35gk.fsf_-_@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=tihirvon@gmail.com \
--cc=torvalds@osdl.org \
/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).