From: "Scott R. Godin" <scottg.wp-hackers@mhg2.com>
To: git@vger.kernel.org
Subject: merge --no-commit not able to report stats more verbosely?
Date: Mon, 22 Oct 2012 09:39:31 -0400 [thread overview]
Message-ID: <k63iai$kbp$1@ger.gmane.org> (raw)
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?
(develop)>$ git merge --no-commit --stat -v widget_twitter
Automatic merge went well; stopped before committing as requested
(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(-)
(develop)>$ git --version
git version 1.7.7.6
--
(please respond to the list as opposed to my email box directly,
unless you are supplying private information you don't want public
on the list)
next reply other threads:[~2012-10-22 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 13:39 Scott R. Godin [this message]
2012-10-26 17:18 ` merge --no-commit not able to report stats more verbosely? Scott R. Godin
2012-10-28 11:21 ` Jeff King
2012-10-29 18:12 ` Phil Hord
2012-10-29 21:51 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='k63iai$kbp$1@ger.gmane.org' \
--to=scottg.wp-hackers@mhg2.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).