All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>, git@vger.kernel.org
Subject: Re: 3 failures on test t9100 (svn)
Date: Wed, 03 Mar 2010 12:01:46 -0800	[thread overview]
Message-ID: <7vr5o1p42d.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100303172302.GA10168@coredump.intra.peff.net> (Jeff King's message of "Wed\, 3 Mar 2010 12\:23\:02 -0500")

Jeff King <peff@peff.net> writes:

> On Wed, Mar 03, 2010 at 01:58:04AM +0100, Nicolas Sebrecht wrote:
>
>> >   GIT_TEST_CMP='diff -u'
>> >   test_cmp() {
>> >     $GIT_TEST_CMP "$@"
>> >   }
>> > 
>> > which _should_ split the "diff -u" on whitespace.
>> 
>> I've tried with these exact lines without more success.
>
> That's weird. Can you test this in each of your shells:
>
>   foo() {
>     echo "in foo, arg=$1"
>   }
>   VARIABLE='foo bar'
>   $VARIABLE
>
> It should print "in foo, arg=bar". If it doesn't, then the shell is
> broken.

The only other possibility I can think of is if somebody futz with IFS, in
order to e.g. use the "word splitting" logic for "line splitting" (or
"split at colon"), and forgets to restore the original value.

      parent reply	other threads:[~2010-03-03 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 19:45 3 failures on test t9100 (svn) Nicolas Sebrecht
2010-03-02 21:28 ` Jeff King
2010-03-03  0:58   ` Nicolas Sebrecht
2010-03-03  9:22     ` git-svn died of signal 11 (was "3 failures on test t9100 (svn)") Nicolas Sebrecht
2010-03-03 17:31       ` Jeff King
2010-03-03 21:24         ` Nicolas Sebrecht
2010-03-03 17:23     ` 3 failures on test t9100 (svn) Jeff King
2010-03-03 19:52       ` Nicolas Sebrecht
2010-03-03 20:01       ` Junio C Hamano [this message]

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=7vr5o1p42d.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nicolas.s.dev@gmx.fr \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.