From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Tue, 27 May 2008 10:53:43 GMT
Subject: Re: [RFC/PATCH] git-what: explain what to do next
Message-ID: <alpine.DEB.1.00.0805271151430.30431@racer>
In-Reply-To: <1211877299-27255-1-git-send-email-sbejar@gmail.com>

Hi,

On Tue, 27 May 2008, Santi Béjar wrote:

> In case you don't know the next step, if it is "git commit",
> "git commit --amend", "git rebase --continue" or something else.

We had a patch similar to this already, but I think that the right 
approach is _not_ to teach the single commands to explain their state, but 
to make a new script guessing the current state.  AFAIR we have something 
like that in the completions already, as an (optional) prompt.

However, I think it would make sense to push for that 
.dotest,.git/.dotest-merge -> .git/rebase change _before_ having anything 
like git-whazzup.sh.

Ciao,
Dscho