Re: git UI nit

From: Jakub Narebski <jnareb@gmail.com>
Date: Dec 6, 2006, 15:36 UTC
Message-ID: <el6nul$58n$2@sea.gmane.org>
In-Reply-To: <Pine.LNX.4.63.0612061619120.28348@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:

Show 12 quoted lines

> On Wed, 6 Dec 2006, Han-Wen Nienhuys wrote:
> 
>> Johannes Schindelin escreveu:
>>>                     }
>>>                     if (quiet)
>>>                             continue;
>>> -                   printf("%s: needs update\n", ce->name);
>>> +                   printf("%s: dirty; needs commit\n", ce->name);
>> 
>> Yes - I'd just mention revert as an option too. 
> 
> Actually, I like it that short.

So why not simply use "%s: dirty\n"?

> We had an email on this list, where the poster said he could not merge 
> with Git. It turned out that the merge failed with conflicts, but he 
> did not bother reading through the messages, apparently because they were 
> too many.

Some of that stems from the "pipeline" model / implementation of git commands, where every separate stage spews it's own warning and error messages.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git