[PATCH] t2203: fix wrong commit command

Add commit message to avoid commit's aborting due to the lack of
commit message, not because there are INTENT_TO_ADD entries in index.

Signed-off-by: Nguyễn Thái Ngọc Duy <redacted>
---
 t/t2203-add-intent.sh |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/t/t2203-add-intent.sh b/t/t2203-add-intent.sh
index 58a3299..2543529 100755
--- a/t/t2203-add-intent.sh
+++ b/t/t2203-add-intent.sh

@@ -41,7 +41,7 @@ test_expect_success 'cannot commit with i-t-a entry' '
 	echo frotz >nitfol &&
 	git add rezrov &&
 	git add -N nitfol &&
-	test_must_fail git commit
+	test_must_fail git commit -m initial
 '
 
 test_expect_success 'can commit with an unrelated i-t-a entry in index' '

-- 
1.7.3.1.256.g2539c.dirty

Hi Duy,

Nguyễn Thái Ngọc Duy wrote:

Add commit message to avoid commit's aborting due to the lack of
commit message, not because there are INTENT_TO_ADD entries in index.

Is there any way to differentiate between the two kinds of errors, so
that we can avoid this in the future?  Can we grep the error message
for something, or inspect the exit status?

-- Ram

2012/1/11 Ramkumar Ramachandra [off-list ref]:

Hi Duy,

Nguyễn Thái Ngọc Duy wrote:

quoted

Add commit message to avoid commit's aborting due to the lack of
commit message, not because there are INTENT_TO_ADD entries in index.

Is there any way to differentiate between the two kinds of errors, so
that we can avoid this in the future?  Can we grep the error message
for something, or inspect the exit status?

commit exits with 1 in both cases, so no.
-- 
Duy

On Wed, Jan 11, 2012 at 11:43 AM, Nguyen Thai Ngoc Duy
[off-list ref] wrote:

2012/1/11 Ramkumar Ramachandra [off-list ref]:

quoted

Hi Duy,

Nguyễn Thái Ngọc Duy wrote:

quoted

Add commit message to avoid commit's aborting due to the lack of
commit message, not because there are INTENT_TO_ADD entries in index.

Is there any way to differentiate between the two kinds of errors, so
that we can avoid this in the future?  Can we grep the error message
for something, or inspect the exit status?

commit exits with 1 in both cases, so no.

but grepping error message should work, sorry I hit send too fast
-- 
Duy