Re: [PATCH] git-explain

From: Junio C Hamano <junkio@cox.net>
Date: Dec 5, 2006, 23:07 UTC
Message-ID: <7vslfudjsa.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <46a038f90612051500w44438f70y3c7d1c99998d16bb@mail.gmail.com>

"Martin Langhoff" <martin.langhoff@gmail.com> writes:

Show 12 quoted lines

> On 12/5/06, Jakub Narebski <jnareb@gmail.com> wrote:
>> Junio C Hamano wrote:
>>
>> > [PATCH] git-explain
>> >
>> > This patch adds "git-explain" script that notices various clues
>> > other commands can leave the working tree and repository in and
>> > intended to guide the end user out of the confused mess.
>>
>> I like it, although I think that it explains a bit too little
>
> I like what it does too... but why not as part of git-status?

The biggest reason was that it is a demonstration of concepts, not replacement of anything. Maybe "git status" can be replaced with something like that if people worked on it enough.

The current use of "git status" inside "git commit" needs to be revamped if we pursue this further, though. Because one of the points the "what state is this repository in" check "explain" does is to define what operations are sensible in each state, and most likely in many state it would not make _any_ sense to run "git commit" (say, in the middle of "bisect").