From: Raimund Bauer <ray@softwarelandschaft.com>
Date: Tue, 05 Dec 2006 09:11:30 GMT
Subject: RE: [PATCH] git-explain
Message-ID: <001b01c7184d$5d142c20$0b0aa8c0@abf.local>
In-Reply-To: <7v1wnekh6a.fsf@assigned-by-dhcp.cox.net>

> An issue with this approach is that this can be the beginning 
> of hardwiring the official "right way of doing things" in the 
> set of tools.  Pursuing this approach would enhance the set 
> of state markers like "FAILED_MERGE" in the example, which means:

Wouldn't it be better to create some kind of action-log (that's
cleared at the end of the command if everything was all right)
instead of creating special markers for different commands?

That way there would be only 1 place to check for what happened ...

-- 
best regards

  Ray