git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Aguilar <davvid@gmail.com>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 08/10] git-mergetool.sh: don't use the -a or -b option with the test command
Date: Fri, 16 May 2014 01:24:39 -0700	[thread overview]
Message-ID: <20140516082438.GA2673@gmail.com> (raw)
In-Reply-To: <1400163457-28285-8-git-send-email-gitter.spiros@gmail.com>

On Thu, May 15, 2014 at 07:17:35AM -0700, Elia Pinto wrote:
> Even though POSIX.1 lists -a/-o as options to "test", they are
> marked "Obsolescent XSI". Scripts using these expressions
> should be converted  as follow:
> 
> test "$1" -a "$2"
> 
> should be written as:
> 
> test "$1" && test "$2"
> 
> Likewise
> 
> test "$1" -o "$2"
> 
> should be written as:
> 
> test "$1"  test "$2"
> 
> But note that, in test, -a has higher precedence than -o while
> "&&" and "||" have equal precedence in the shell.
> 
> The reason for this is that the precedence rules were never well
> specified, and this made many sane-looking uses of "test -a/-o" problematic.
> 
> For example, if $x is "=", these work according to POSIX (it's not
> portable, but in practice it's okay):
> 
>    $ test -z "$x"
>    $ test -z "$x" && test a = b
> 
> but this doesn't
> 
>    $ test -z "$x" -a a = b
>    bash: test: too many arguments
> 
> because it groups "test -n = -a" and is left with "a = b".
> 
> Similarly, if $x is "-f", these
> 
>    $ test "$x"
>    $ test "$x" || test c = d
> 
> correctly adds an implicit "-n", but this fails:
> 
>    $ test "$x" -o c = d
>    bash: test: too many arguments
> 
> Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
> ---
> Inspired from this discussion http://permalink.gmane.org/gmane.comp.version-control.git/137056

Looks good, thanks.

Acked-by: David Aguilar <davvid@gmail.com>


>  git-mergetool.sh |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/git-mergetool.sh b/git-mergetool.sh
> index 332528f..88e853f 100755
> --- a/git-mergetool.sh
> +++ b/git-mergetool.sh
> @@ -205,7 +205,7 @@ checkout_staged_file () {
>  		"$(git checkout-index --temp --stage="$1" "$2" 2>/dev/null)" \
>  		: '\([^	]*\)	')
>  
> -	if test $? -eq 0 -a -n "$tmpfile"
> +	if test $? -eq 0 && test -n "$tmpfile"
>  	then
>  		mv -- "$(git rev-parse --show-cdup)$tmpfile" "$3"
>  	else
> @@ -256,7 +256,7 @@ merge_file () {
>  	checkout_staged_file 2 "$MERGED" "$LOCAL"
>  	checkout_staged_file 3 "$MERGED" "$REMOTE"
>  
> -	if test -z "$local_mode" -o -z "$remote_mode"
> +	if test -z "$local_mode" || test -z "$remote_mode"
>  	then
>  		echo "Deleted merge conflict for '$MERGED':"
>  		describe_file "$local_mode" "local" "$LOCAL"
> -- 
> 1.7.10.4
-- 
David

  reply	other threads:[~2014-05-16  8:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 14:17 [PATCH 01/10] check_bindir: don't use the -a or -b option with the test command Elia Pinto
2014-05-15 14:17 ` [PATCH 02/10] contrib/examples/git-clone.sh: " Elia Pinto
2014-05-15 14:17 ` [PATCH 03/10] contrib/examples/git-commit.sh: " Elia Pinto
2014-05-15 14:17 ` [PATCH 04/10] contrib/examples/git-merge.sh: " Elia Pinto
2014-05-15 14:17 ` [PATCH 05/10] contrib/examples/git-repack.sh: " Elia Pinto
2014-05-15 14:17 ` [PATCH 06/10] contrib/examples/git-resolve.sh: " Elia Pinto
2014-05-15 14:17 ` [PATCH 07/10] git-bisect.sh: " Elia Pinto
2014-05-15 14:17 ` [PATCH 08/10] git-mergetool.sh: " Elia Pinto
2014-05-16  8:24   ` David Aguilar [this message]
2014-05-15 14:17 ` [PATCH 09/10] git-rebase--interactive.sh: " Elia Pinto
2014-05-15 14:17 ` [PATCH 10/10] git-submodule.sh: " Elia Pinto
2014-05-15 14:19   ` Elia Pinto
2014-05-15 15:58   ` Jonathan Nieder
2014-05-16 19:09     ` 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=20140516082438.GA2673@gmail.com \
    --to=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gitter.spiros@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).