All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.3
Date: Sun, 02 Sep 2007 10:43:38 +0200	[thread overview]
Message-ID: <fbdt3q$lcf$1@sea.gmane.org> (raw)
In-Reply-To: 7vodglr32i.fsf@gitster.siamese.dyndns.org

Junio C Hamano wrote:

> The latest feature release GIT 1.5.3 is available at the usual
> places:

Hm,

/usr/bin/make -C t/ all
make[1]: Entering directory `/home/users/arekm/rpm/BUILD/git-1.5.3/t'
*** t0000-basic.sh ***
*   ok 1: .git/objects should be empty after git init in an empty repo.
*   ok 2: .git/objects should have 3 subdirectories.
*   ok 3: git update-index without --add should fail adding.
*   ok 4: git update-index with --add should succeed.
*   ok 5: writing tree out with git write-tree
*   ok 6: validate object ID of a known tree.
*   ok 7: git update-index without --remove should fail removing.
*   ok 8: git update-index with --remove should be able to remove.
*   ok 9: git write-tree should be able to write an empty tree.
*   ok 10: validate object ID of a known tree.
*   ok 11: adding various types of objects with git update-index --add.
*   ok 12: showing stage with git ls-files --stage
*   ok 13: validate git ls-files output for a known tree.
*   ok 14: writing tree out with git write-tree.
*   ok 15: validate object ID for a known tree.
*   ok 16: showing tree with git ls-tree
*   ok 17: git ls-tree output for a known tree.
*   ok 18: showing tree with git ls-tree -r
*   ok 19: git ls-tree -r output for a known tree.
*   ok 20: showing tree with git ls-tree -r -t
*   ok 21: git ls-tree -r output for a known tree.
*   ok 22: writing partial tree out with git write-tree --prefix.
*   ok 23: validate object ID for a known tree.
*   ok 24: writing partial tree out with git write-tree --prefix.
*   ok 25: validate object ID for a known tree.
*   ok 26: put invalid objects into the index.
*   ok 27: writing this tree without --missing-ok.
*   ok 28: writing this tree with --missing-ok.
*   ok 29: git read-tree followed by write-tree should be idempotent.
*   ok 30: validate git diff-files output for a know cache/work tree state.
*   ok 31: git update-index --refresh should succeed.
*   ok 32: no diff after checkout and git update-index --refresh.
*   ok 33: git commit-tree records the correct tree in a commit.
*   ok 34: git commit-tree records the correct parent in a commit.
*   ok 35: git commit-tree omits duplicated parent in a commit.
*   ok 36: update-index D/F conflict
*   ok 37: absolute path works as expected
* passed all 37 test(s)
*** t0001-init.sh ***
* FAIL 1: plain

                (
                        unset GIT_DIR GIT_WORK_TREE &&
                        mkdir plain &&
                        cd plain &&
                        git init
                ) &&
                check_config plain/.git false unset

*   ok 2: plain with GIT_WORK_TREE
* FAIL 3: plain bare

                (
                        unset GIT_DIR GIT_WORK_TREE GIT_CONFIG &&
                        mkdir plain-bare-1 &&
                        cd plain-bare-1 &&
                        git --bare init
                ) &&
                check_config plain-bare-1 true unset

*   ok 4: plain bare with GIT_WORK_TREE
*   ok 5: GIT_DIR bare
*   ok 6: GIT_DIR non-bare
*   ok 7: GIT_DIR & GIT_WORK_TREE (1)
*   ok 8: GIT_DIR & GIT_WORK_TREE (2)
* failed 2 among 8 test(s)
make[1]: *** [t0001-init.sh] Error 1
make[1]: Leaving directory `/home/users/arekm/rpm/BUILD/git-1.5.3/t'

verified on 2 machines (so /dev/ is ok this time)

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

  parent reply	other threads:[~2007-09-02  8:55 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 [this message]
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
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='fbdt3q$lcf$1@sea.gmane.org' \
    --to=arekm@pld-linux.org \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@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.