git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: t5801-remote-helpers.sh fails
Date: Sat, 10 Nov 2012 20:20:14 +0100	[thread overview]
Message-ID: <509EA8EE.1030908@web.de> (raw)
In-Reply-To: <CAMP44s0HtMRaQ91z95cZS73W7tnqYwyKV_2guWJ6u6UP4p5JNw@mail.gmail.com>

On 11/10/2012 08:15 PM, Felipe Contreras wrote:
> Hi,
>
> On Sat, Nov 10, 2012 at 2:48 PM, Torsten Bögershausen <tboegi@web.de> wrote:
>
>> on peff/pu t5801 fails, the error is in git-remote-testgit, please see below.
>>
>> That's on my Mac OS X box.
>>
>> I haven't digged further into the test case, but it looks as if
>> "[-+]A  make NAMEs associative arrays"
>> is not supported on this version of bash.
>> /Torsten
>>
>>
>> /Users/tb/projects/git/git.peff/git-remote-testgit: line 64: declare: -A: invalid option
>> declare: usage: declare [-afFirtx] [-p] [name[=value] ...]
>> /Users/tb/projects/git/git.peff/git-remote-testgit: line 66: refs/heads/master: division by 0 (error token is "/master")
>> error: fast-export died of signal 13
>> fatal: Error while running fast-export
>
> What is your bash --version?
>
  bash --version
GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0)
Copyright (C) 2007 Free Software Foundation, Inc.

On the other hand, Documentation/CodingGuidelines says:
   - No shell arrays.

Could we use perl to have arrays?

/Torsten

  reply	other threads:[~2012-11-10 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10 13:48 t5801-remote-helpers.sh fails Torsten Bögershausen
2012-11-10 19:15 ` Felipe Contreras
2012-11-10 19:20   ` Torsten Bögershausen [this message]
2012-11-10 22:05     ` Felipe Contreras
2012-11-18  5:50       ` Torsten Bögershausen
2012-11-18  8:23         ` Felipe Contreras
2012-11-18 15:52           ` Torsten Bögershausen

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=509EA8EE.1030908@web.de \
    --to=tboegi@web.de \
    --cc=felipe.contreras@gmail.com \
    --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).