git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Andreas Ericsson <ae@op5.se>,
	git@vger.kernel.org, Sam Vilain <sam@vilain.net>
Subject: Re: Building git-1.5.3.7 on HP-UX 11.00
Date: Tue, 4 Dec 2007 23:25:42 +0100	[thread overview]
Message-ID: <20071204232542.425d2ead@pc09.procura.nl> (raw)
In-Reply-To: <7vve7e49or.fsf@gitster.siamese.dyndns.org>

On Tue, 04 Dec 2007 10:05:40 -0800, Junio C Hamano <gitster@pobox.com> wrote:

> "H.Merijn Brand" <h.m.brand@xs4all.nl> writes:
> 
> > On Tue, 4 Dec 2007 15:39:47 +0000 (GMT), Johannes Schindelin
> > ...
> > I found it! unset returns false
> > ...
> > I must leave now.
> 
> Thanks, you two.
> 
> I do not see "unset VAR... &&" outside t0001 test, but there are
> instances of "unset VAR... &&" in git-submodule implementations as well.
> 
> In short, not too many places to fix.

Going from there ....

# make test
:
:
:
*** t1300-repo-config.sh ***
*   ok 1: initial
*   ok 2: mixed case
*   ok 3: similar section
*   ok 4: similar section
*   ok 5: replace with non-match
*   ok 6: replace with non-match (actually matching)
*   ok 7: non-match result
*   ok 8: multiple unset
*   ok 9: multiple unset is correct
*   ok 10: --replace-all
*   ok 11: all replaced
*   ok 12: really mean test
*   ok 13: really really mean test
*   ok 14: get value
*   ok 15: unset
*   ok 16: multivar
* FAIL 17: non-match
        git config --get nextsection.nonewline !for
* FAIL 18: non-match value
        test wow = $(git config --get nextsection.nonewline !for)
*   ok 19: ambiguous get
*   ok 20: get multivar
*   ok 21: multivar replace
*   ok 22: ambiguous value
*   ok 23: ambiguous unset
*   ok 24: invalid unset
*   ok 25: multivar unset
*   ok 26: invalid key
*   ok 27: correct key
*   ok 28: hierarchical section
*   ok 29: hierarchical section value
*   ok 30: working --list
*   ok 31: --get-regexp
*   ok 32: --add
*   ok 33: get variable with no value
*   ok 34: get-regexp variable with no value
*   ok 35: no arguments, but no crash
*   ok 36: new section is partial match of another
*   ok 37: new variable inserts into proper section
*   ok 38: alternative GIT_CONFIG (non-existing file should fail)
*   ok 39: alternative GIT_CONFIG
*   ok 40: alternative GIT_CONFIG (--file)
*   ok 41: --set in alternative GIT_CONFIG
*   ok 42: rename section
*   ok 43: rename succeeded
*   ok 44: rename non-existing section
*   ok 45: rename succeeded
*   ok 46: rename another section
*   ok 47: rename succeeded
*   ok 48: remove section
*   ok 49: section was removed properly
*   ok 50: section ending
*   ok 51: numbers
*   ok 52: bool
*   ok 53: invalid bool (--get)
*   ok 54: invalid bool (set)
*   ok 55: set --bool
*   ok 56: set --int
*   ok 57: quoting
*   ok 58: key with newline
*   ok 59: value with newline
*   ok 60: value continued on next line
* FAIL 61: --null --list
        cmp result expect
* FAIL 62: --null --get-regexp
        cmp result expect
*   ok 63: symlinked configuration
* failed 4 among 63 test(s)


-- 
H.Merijn Brand         Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.10.x  on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin.       http://qa.perl.org
http://mirrors.develooper.com/hpux/            http://www.test-smoke.org
                        http://www.goldmark.org/jeff/stupid-disclaimers/

  reply	other threads:[~2007-12-04 22:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 13:09 Building git-1.5.3.7 on HP-UX 11.00 H.Merijn Brand
2007-12-04 13:44 ` Johannes Schindelin
2007-12-04 14:03   ` H.Merijn Brand
2007-12-04 14:40     ` Johannes Schindelin
2007-12-04 15:01       ` H.Merijn Brand
2007-12-04 15:14         ` Andreas Ericsson
2007-12-04 15:22           ` H.Merijn Brand
2007-12-04 15:39             ` Johannes Schindelin
2007-12-04 15:56               ` H.Merijn Brand
2007-12-04 16:28                 ` Johannes Schindelin
2007-12-05 10:49                   ` H.Merijn Brand
2007-12-04 18:05                 ` Junio C Hamano
2007-12-04 22:25                   ` H.Merijn Brand [this message]
2007-12-04 22:46                     ` Johannes Schindelin
2007-12-05  8:08                       ` H.Merijn Brand
2007-12-04 22:45                   ` [PATCH] Do not rely on the exit status of "unset" for unset variables Johannes Schindelin
2007-12-05  8:01                     ` H.Merijn Brand
2007-12-10 14:51                   ` Building git-1.5.3.7 on HP-UX 11.00 H.Merijn Brand
2007-12-11  8:26                     ` Junio C Hamano
2007-12-11  8:54                       ` Shawn O. Pearce
2007-12-11 12:57                         ` H.Merijn Brand
2007-12-11  9:20                       ` Johannes Sixt
2007-12-11 10:42                         ` H.Merijn Brand
2007-12-11 11:01                           ` Johannes Sixt
2007-12-11 13:33                       ` H.Merijn Brand
2007-12-11 13:53                         ` Johannes Sixt
2007-12-04 15:11       ` H.Merijn Brand

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=20071204232542.425d2ead@pc09.procura.nl \
    --to=h.m.brand@xs4all.nl \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sam@vilain.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 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).