Re: [PATCH] t2203: fix wrong commit command

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Jan 11, 2012, 04:43 UTC
Message-ID: <CACsJy8Dkcj4Vbow29SBW52JKu7bkEWzk_S=rTrG+fdxiD0w7xw@mail.gmail.com>
In-Reply-To: <CACsJy8CjWBRtj3x3guyu-iJeTYxcRriXKbE=Be-rG=Rmesgt=g@mail.gmail.com>

On Wed, Jan 11, 2012 at 11:43 AM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:

Show 12 quoted lines

> 2012/1/11 Ramkumar Ramachandra <artagnon@gmail.com>:
>> 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?
>
> commit exits with 1 in both cases, so no.

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

-- 
Duy