Re: [RFC/PATCH] git-what: explain what to do next

From: Santi Béjar <sbejar@gmail.com>
Date: May 27, 2008, 12:58 UTC
Message-ID: <8aa486160805270558v40e7faabh7d4426731693f917@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0805271151430.30431@racer>

On Tue, May 27, 2008 at 12:53 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 10 quoted lines

> 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.

I think it belongs to each command to know the state, but I have no problem with the single command approach.

>  AFAIR we have something
> like that in the completions already, as an (optional) prompt.

Thanks. And they do it a bit different, I'll use it if it is better than mine.

>
> 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.

That's a problem of the single command approach.

Santi