From: Jeff King <peff@peff.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] test-lib: quote TRASH_DIRECTORY
Date: Fri, 4 Mar 2016 06:51:28 -0500 [thread overview]
Message-ID: <20160304115127.GA8355@sigill.intra.peff.net> (raw)
In-Reply-To: <a07529d116612bcd1c411a697f8f8e37d7c18d3f.1457088499.git.git@drmicha.warpmail.net>
On Fri, Mar 04, 2016 at 11:53:49AM +0100, Michael J Gruber wrote:
> We always quote $TRASH_DIRECTORY to guard against funky path names. Do
> so in one more spot
>
> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
> ---
> t/test-lib.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/t/test-lib.sh b/t/test-lib.sh
> index 0b47eb6..8957916 100644
> --- a/t/test-lib.sh
> +++ b/t/test-lib.sh
> @@ -868,7 +868,7 @@ case "$TRASH_DIRECTORY" in
> /*) ;; # absolute path is good
> *) TRASH_DIRECTORY="$TEST_OUTPUT_DIRECTORY/$TRASH_DIRECTORY" ;;
> esac
> -test ! -z "$debug" || remove_trash=$TRASH_DIRECTORY
> +test ! -z "$debug" || remove_trash="$TRASH_DIRECTORY"
I don't think this does anything. The shell doesn't do whitespace
splitting on the right-hand side of a variable assignment:
$ foo='lots of spaces and "!'\'' funky chars'
$ bar=$foo
$ echo "$bar"
lots of spaces and "!' funky chars
Of course we _do_ need quotes when we refer to $remove_trash as an
argument (as with "$bar" above), but it looks like we do so correctly
everywhere.
-Peff
next prev parent reply other threads:[~2016-03-04 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 10:53 [PATCH/RFC 0/2] Test trash dir sanitizing Michael J Gruber
2016-03-04 10:53 ` [PATCH 1/2] test-lib: quote TRASH_DIRECTORY Michael J Gruber
2016-03-04 11:51 ` Jeff King [this message]
2016-03-04 13:03 ` Michael J Gruber
2016-03-04 13:09 ` Jeff King
2016-03-04 10:53 ` [PATCH 2/2] t5510: do not leave changed cwd Michael J Gruber
2016-03-04 11:52 ` Jeff King
2016-03-04 13:04 ` Michael J Gruber
2016-03-04 18:38 ` Junio C Hamano
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=20160304115127.GA8355@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.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).