From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: git diff with add/modified codes
Date: Fri, 27 Jul 2007 20:17:54 -0400 [thread overview]
Message-ID: <9e4733910707271717q5ea33b55r227d8dbb1023de47@mail.gmail.com> (raw)
In-Reply-To: <7vir85whxy.fsf@assigned-by-dhcp.cox.net>
On 7/27/07, Junio C Hamano <gitster@pobox.com> wrote:
> Would --stat --summary be satisfactory?
That's not what I want. I'm looking a report that indicates new files
vs modified ones in a single list. These old patches I am working with
often create 100 files and modify another 200.
Adding a code like (Added (A), Copied (C), Deleted (D), Modified (M),
Renamed (R)) to --stat would be perfect.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-07-28 0:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 22:05 git diff with add/modified codes Jon Smirl
2007-07-27 23:22 ` Junio C Hamano
2007-07-28 0:17 ` Jon Smirl [this message]
2007-07-28 4:39 ` Jeff King
2007-07-28 15:26 ` Jakub Narebski
2007-07-28 18:07 ` Jon Smirl
2007-07-29 21:36 ` Jakub Narebski
2007-07-28 0:48 ` Johannes Schindelin
2007-07-28 0:54 ` Jon Smirl
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e4733910707271717q5ea33b55r227d8dbb1023de47@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
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 NNTP newsgroup(s).