All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git diff with add/modified codes
Date: Sat, 28 Jul 2007 17:26:27 +0200	[thread overview]
Message-ID: <f8fn72$l30$1@sea.gmane.org> (raw)
In-Reply-To: 20070728043901.GB11916@coredump.intra.peff.net

Jeff King wrote:

> On Fri, Jul 27, 2007 at 08:17:54PM -0400, Jon Smirl wrote:
> 
>> 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.
> 
> How about --name-status?

Or -r --name-status?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-07-28 15:26 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
2007-07-28  4:39     ` Jeff King
2007-07-28 15:26       ` Jakub Narebski [this message]
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='f8fn72$l30$1@sea.gmane.org' \
    --to=jnareb@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.