git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: Benoit Sigoure <tsuna@lrde.epita.fr>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Fix and improve t7004
Date: Fri, 16 Nov 2007 22:35:38 +0100	[thread overview]
Message-ID: <20071116213538.GA30076@glandium.org> (raw)
In-Reply-To: <EC3B30DC-E81C-4ECA-BE7F-F237E1338603@lrde.epita.fr>

On Fri, Nov 16, 2007 at 10:31:15PM +0100, Benoit Sigoure wrote:
> On Nov 16, 2007, at 10:11 PM, Mike Hommey wrote:
>
>> On Fri, Nov 16, 2007 at 10:04:57PM +0100, Benoit Sigoure wrote:
>>> On Nov 16, 2007, at 9:28 PM, Mike Hommey wrote:
>>>>  test_expect_success \
>>>>  	'message in editor has initial comment' '
>>>>  	GIT_EDITOR=cat git tag -a initial-comment > actual || true &&
>>>> -	test $(sed -n "/^\(#\|\$\)/p" actual | wc -l) -gt 0
>>>> +	( read empty ;
>>>> +	  [ "$empty" ] && exit 1 ;
>>>
>>> What is this meant to do?  Did you mean [ -n "$empty" ] ?
>>
>> Replacing with [ -n "$empty" ] would not work properly, except if you
>> replace the following ; with &&. Does that really make a readability
>> difference ?
>
> I don't get it.  As far as I understand, you're trying to check whether 
> $empty is indeed empty, right?  So how is `[ "$empty" ]' meant to work?
>   [ -n "$empty" ] && exit 1
>
> will exit 1 if empty isn't empty.

Sorry, I read '-z', not '-n'. [ "$empty" ] and [ -n "$empty" ] are the
same thing.

Mike

  reply	other threads:[~2007-11-16 21:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 13:38 [BUG] t7004 (master) busted on Leopard Wincent Colaiuta
2007-11-15 14:37 ` Johannes Schindelin
2007-11-15 14:48   ` David Kastrup
2007-11-15 15:12   ` Wincent Colaiuta
2007-11-15 15:16   ` [PATCH] Fix git-tag test breakage caused by broken sed " Wincent Colaiuta
2007-11-15 15:47     ` [PATCH v2] " Wincent Colaiuta
     [not found]       ` <7v4pfm3h6f.fsf@gitster.siamese.dyndns.org>
2007-11-16 13:45         ` Wincent Colaiuta
2007-11-16 13:48           ` Wincent Colaiuta
2007-11-16 16:59             ` Mike Hommey
2007-11-16 17:25               ` Wincent Colaiuta
2007-11-16 17:26               ` [PATCH] Fix t7004 which fails with retarded sed Mike Hommey
2007-11-16 17:58                 ` Benoit Sigoure
2007-11-16 19:15                   ` Mike Hommey
2007-11-16 18:02                 ` Wincent Colaiuta
2007-11-16 18:26                 ` Junio C Hamano
2007-11-16 19:17                   ` Mike Hommey
2007-11-16 19:36                     ` Junio C Hamano
2007-11-16 20:28                       ` [PATCH] Fix and improve t7004 Mike Hommey
2007-11-16 21:04                         ` Benoit Sigoure
2007-11-16 21:11                           ` Mike Hommey
2007-11-16 21:31                             ` Benoit Sigoure
2007-11-16 21:35                               ` Mike Hommey [this message]
2007-11-16 21:47                                 ` Benoit Sigoure
2007-11-16 21:42                             ` Junio C Hamano
2007-11-16 22:02                               ` Mike Hommey
2007-11-17  8:55                                 ` 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=20071116213538.GA30076@glandium.org \
    --to=mh@glandium.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tsuna@lrde.epita.fr \
    /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).