2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:06
Johannes Schindelin [off-list ref] writes:
If you're up for a very surprising error message, run the test without compiling git-add first...
$ PATH=/usr/bin:/bin sh t3700-add.sh -i -v
* expecting success: touch foo && git-add foo
./test-lib.sh: line 136: git-add: command not found
* FAIL 1: Test of git-add
touch foo && git-add foo
$ echo $?
1
From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:43:06
Hi, On Mon, 23 Apr 2007, Junio C Hamano wrote:
Johannes Schindelin [off-list ref] writes:quoted
If you're up for a very surprising error message, run the test without compiling git-add first...$ PATH=/usr/bin:/bin sh t3700-add.sh -i -v * expecting success: touch foo && git-add foo ./test-lib.sh: line 136: git-add: command not found * FAIL 1: Test of git-add touch foo && git-add foo $ echo $? 1
;-)
I did not say you should "make clean" first... For the record: this is
what the surprising error looks like on my machine:
* expecting success:
git add 1/2/a 1/3/b 1/2/c
The following paths are ignored by one of your .gitignore files:
1/3/b
Use -f if you really want to add them.
* FAIL 15: check correct prefix detection
The surprising factor is, of course, that there is no .gitignore file.
Ciao,
Dscho