Re: merge --no-commit not able to report stats more verbosely?

From: Phil Hord <phil.hord@gmail.com>
Date: Oct 29, 2012, 18:12 UTC
Message-ID: <CABURp0oX5aT=yEbYeDXoOPWj_aRscVBY327_E6uyrrp5TPvcxA@mail.gmail.com>
In-Reply-To: <20121028112150.GD11434@sigill.intra.peff.net>

On Sun, Oct 28, 2012 at 7:21 AM, Jeff King <peff@peff.net> wrote:

Show 28 quoted lines

> On Mon, Oct 22, 2012 at 09:39:31AM -0400, Scott R. Godin wrote:
>
>> As you can see from the below, I can't seem to get it to give me more
>> verbose results of what's being merged (as in the actual merge below)
>> with --stat or -v .. is it supposed to do that?
>
> Yes. The diffstat is shown for the completed merge, but here:
>
>> (develop)>$ git merge --no-commit --stat -v widget_twitter
>> Automatic merge went well; stopped before committing as requested
>
> You do not complete the merge.
>
>> (develop|MERGING)>$ git merge --abort
>>
>> (develop)>$ git merge widget_twitter
>> Merge made by the 'recursive' strategy.
>>  .../code/community/Dnd/Magentweet/Model/User.php   |    3 ++-
>>  1 files changed, 2 insertions(+), 1 deletions(-)
>
> Whereas here you do, and you get a diffstat.
>
> When you are in the middle of an uncompleted merge and want to know what
> is happening, you should look at the index using "git status" (to get an
> overview of what is ready to be committed and what is unmerged), "git
> diff --cached" (to see what was automatically merged and is ready for
> commit), and "git diff" (to see conflicted entries that still need to be
> resolved).

I think he is looking for this bit
    "Merge made by the 'recursive' strategy."

But he is seeing this instead:
    "Automatic merge went well; stopped before committing as requested"

Should the "what happened" output be silenced on --no-commit?

Phil