All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.3
Date: Sun, 02 Sep 2007 14:36:02 +0200	[thread overview]
Message-ID: <fbeanj$mfq$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0709021157120.28586@racer.site

Johannes Schindelin wrote:

> Hi,
> 
> On Sun, 2 Sep 2007, Arkadiusz Miskiewicz wrote:
> 
>> Junio C Hamano wrote:
>> 
>> > The latest feature release GIT 1.5.3 is available at the usual
>> > places:
>> 
>> Hm,
>> 
>> [...]
>>
>> *** t0001-init.sh ***
>> * FAIL 1: plain
>> 
>>                 (
>>                         unset GIT_DIR GIT_WORK_TREE &&
>>                         mkdir plain &&
>>                         cd plain &&
>>                         git init
>>                 ) &&
>>                 check_config plain/.git false unset
> 
> Please try the verbose mode: cd t/ && sh t0001-init.sh -i -v.  If that
> does not show you _what_ the problem is, try "sh -x [...]".
> 
> If you still cannot find what the problem is, please tell us what platform
> you're running on, and show us the output of the "-i -v" invocation.

Found out why this happens. My /bin/sh is pdksh (not bash).

AAAA was never set and:

/bin/sh (pdksh)
[arekm@carme-pld ~]$ unset AAAA
[arekm@carme-pld ~]$ echo $?
1

/bin/bash
[arekm@carme-pld ~]$ unset AAAA
[arekm@carme-pld ~]$ echo $?
0

It's pdksh bug, susv3 says "Unsetting a variable or function that was not
previously set shall not be considered an error and does not cause the
shell to abort."

Going to fix pdksh then.

> Ciao,
> Dscho

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

  parent reply	other threads:[~2007-09-02 12:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-02  6:31 [ANNOUNCE] GIT 1.5.3 Junio C Hamano
2007-09-02  6:34 ` A note from the maintainer Junio C Hamano
2007-09-02  6:58 ` [ANNOUNCE] GIT 1.5.3 H. Peter Anvin
2007-09-02  7:58   ` Junio C Hamano
2007-09-02  8:06   ` David Kastrup
2007-09-02  9:57     ` H. Peter Anvin
2007-09-02 17:38       ` Sean
2007-09-02 22:13         ` Junio C Hamano
2007-09-02 23:16           ` Sean
2007-09-03  0:19             ` Junio C Hamano
2007-09-03  7:51             ` H. Peter Anvin
2007-09-03  8:10               ` Junio C Hamano
2007-09-03  8:12                 ` H. Peter Anvin
2007-09-03  8:35                   ` Junio C Hamano
2007-09-03  8:47                     ` H. Peter Anvin
2007-09-03  8:53                       ` Junio C Hamano
2007-09-03  9:10                       ` Junio C Hamano
2007-09-03  9:13                         ` H. Peter Anvin
2007-09-03 11:32           ` Andreas Ericsson
2007-09-03 12:58             ` David Kastrup
2007-09-03 13:02               ` Andreas Ericsson
2007-09-03 13:17                 ` David Kastrup
2007-09-03  7:46         ` H. Peter Anvin
2007-09-02  7:08 ` David Kastrup
2007-09-02  8:43 ` Arkadiusz Miskiewicz
2007-09-02 10:28   ` Alex Riesen
2007-09-02 10:59   ` Johannes Schindelin
2007-09-02 11:19     ` Alex Riesen
2007-09-02 12:36     ` Arkadiusz Miskiewicz [this message]
2007-09-02 15:12 ` Nicolas Vilz
2007-09-02 22:52 ` David Kågedal
2007-09-02 22:54   ` David Kågedal
2007-09-02 23:28     ` Junio C Hamano
2007-09-02 23:36       ` Steven Grimm
2007-09-03  0:03         ` 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='fbeanj$mfq$1@sea.gmane.org' \
    --to=arekm@pld-linux.org \
    --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 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.