From: Sverre Rabbelier <srabbelier@gmail.com>
Date: Fri, 30 Jul 2010 18:44:24 GMT
Subject: Re: Making error messages stand out (Re: [RFC/PATCH 0/9] commit: more focused advice in the no-changes-staged case)
Message-ID: <AANLkTi=ao2RY8NGm4cACqz3_5zfT2zvXB4JHOopBD9T5@mail.gmail.com>
In-Reply-To: <20100729235151.GB6623@burratino>

Heya,

On Thu, Jul 29, 2010 at 18:51, Jonathan Nieder <jrnieder@gmail.com> wrote:
> though, I find the best solution is to use short, formulaic messages:
>
>  ...
>  Recorded resolution for 'dir/a'.
>  [detached HEAD aa9ae6b] related change
>   1 files changed, 1 insertions(+), 1 deletions(-)
>  fatal: could not apply 649420f... second
>  hint: after resolving the conflicts, mark the corrected paths
>  hint: with 'git add <paths>' and run 'git rebase --continue'

Yes please. This would be _extremely_ helpful!

-- 
Cheers,

Sverre Rabbelier