Another "hg diff" annoyance

[Steve Borho]

On Fri, May 22, 2009 at 12:24 AM, Greg Lindahl <greg at blekko.com> wrote:
> On Thu, May 21, 2009 at 10:18:12PM -0700, Peter Hosey wrote:
>
>> An alternative solution would be to add a summary of the uncommitted
>> changes to the command that raised the error. Something like:
>>
>>       abort: uncommitted changes
>>       ? foo.txt
>>       1 file(s) missing; did you forget to hg remove them?
>
> Yes, that would be good. "uncommitted changes" really isn't a good
> description of what's going on... if it was, then committing ought to
> fix it. But it doesn't.

+1
At the least, it could suggest the user to run 'hg status' to discover
the uncomitted changes.

--
Steve Borho