All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Krüger" <matthias.krueger@famsik.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: gitdiffbinstat  -  git diff --shortstat -like output for changes in binary files
Date: Fri, 29 Mar 2013 20:22:48 +0100	[thread overview]
Message-ID: <5155EA08.60005@famsik.de> (raw)
In-Reply-To: <20130329184922.GB13506@sigill.intra.peff.net>

On 03/29/2013 07:49 PM, Jeff King wrote:
> On Fri, Mar 29, 2013 at 07:07:32PM +0100, Matthias Krüger wrote:
>
>> I use git mostly for game-development which means I have to deal with
>> a lot of binary files (images, sound files etc).
>>
>> When I came to a point where I had run image optimization on a
>> branch, I wanted to know of course how much smaller the new branch
>> was in comparison to master.
>> Problem was that 'git diff --stat' would only summerize
>> per-binary-file size changes and 'git diff --shortstat' did skip the
>> binary files entirely.
> Have you tried "--summary"? Combined with --stat (or --shortstat) I
> wonder if it would get you closer to what you want.
>
> -Peff
No it doesnt.
It appears to append stuff like

  delete mode 100644 sound/music/NewTutorialStage.ogg
  delete mode 100644 src/pngfuncs.c
  delete mode 100644 src/pngfuncs.h
  delete mode 100644 src/widgets/widget_text_list.c
  delete mode 100644 src/widgets/widget_text_list.h

to the stat but does not summarize the binary file size changes.

  reply	other threads:[~2013-03-29 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 18:07 gitdiffbinstat - git diff --shortstat -like output for changes in binary files Matthias Krüger
2013-03-29 18:49 ` Jeff King
2013-03-29 19:22   ` Matthias Krüger [this message]
2013-03-29 19:30   ` Junio C Hamano

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=5155EA08.60005@famsik.de \
    --to=matthias.krueger@famsik.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.