Re: [RFE] git rebase doesn't say it failed

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 10, 2008, 11:10 UTC
Message-ID: <alpine.LSU.1.00.0803101207120.3975@racer.site>
In-Reply-To: <429AC7A2-511E-496F-9C1C-4627604EBBFB@gmail.com>

Hi,

On Sun, 9 Mar 2008, Christian Holtje wrote:

Show 5 quoted lines

> Hello!
> 
> What happened:
> I tried to do a rebase and got a message about files "needs update".
> However, it didn't say it did a rebase nor did it say that it failed.

It told you that a file is dirty. Git kinda expects you to know that it will not start a rebase on a dirty working directory.

So there _was_ an (implicit) message saying that it failed.

> Git was unable to rebase due to the files above.  Please commit them or move
> them out of the way.
> Hint: See "git reset --help" for a suggestion about saving work in progress.

The same comment I gave last week applies here: people complained that Git was too chatty. I tend to agree, since the important information was lost in the huge amount of text. Now you say we should make it chatty again?

Hth, Dscho