From: Rogan Dawes <lists@dawes.za.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Show binary file size change in diff --stat
Date: Wed, 04 Apr 2007 15:34:44 +0200 [thread overview]
Message-ID: <4613A974.60808@dawes.za.net> (raw)
In-Reply-To: <200704041414.14797.andyparkins@gmail.com>
Andy Parkins wrote:
> Previously, a binary file in the diffstat would show as:
>
> some-binary-file.bin | Bin
>
> The space after the "Bin" was never used. This patch changes binary
> lines in the diffstat to be:
>
> some-binary-file.bin | Bin 12345 -> 123456 bytes
>
> The very nice "->" notation was suggested by Johannes Schindelin, and
> shows the before and after sizes more clearly than "+" and "-" would.
> If a size is 0 it's not shown (although it would probably be better to
> treat no-file differently from zero-byte-file).
>
> The user can see what changed in the binary file, and how big the new
> file is. This is in keeping with the information in the rest of the
> diffstat.
>
> The diffstat_t members "added" and "deleted" were unused when the file
> was binary, so this patch loads them with the file sizes in
> builtin_diffstat(). These figures are then read in show_stats() when
> the file is marked binary.
>
> Signed-off-by: Andy Parkins <andyparkins@gmail.com>
> ---
> This is a resend; I still wish for it every time I see a --stat with
> binary files changed.
>
> Is there any objection to it that I can address?
Well, how about my comments in <45E67978.9030805@dawes.za.net>,
suggesting that the edit difference (number of steps required to
transform one to the other) would be a better indication?
I think it is better because it is consistent with what we currently do
for text files: show the number of lines added/deleted.
For binary files, it would be consistent to show the number of bytes
added/deleted. I have not investigated the output format for the
libxdiff binary patch format, but hopefully it would not be too
difficult to calculate the deletions and additions.
Rogan
next prev parent reply other threads:[~2007-04-04 13:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 13:14 [PATCH] Show binary file size change in diff --stat Andy Parkins
2007-04-04 13:34 ` Rogan Dawes [this message]
2007-04-04 14:40 ` Geert Bosch
2007-04-04 16:00 ` Rogan Dawes
2007-04-04 14:40 ` Andy Parkins
2007-04-04 15:51 ` Rogan Dawes
2007-04-04 16:22 ` Johannes Schindelin
2007-04-04 16:26 ` Rogan Dawes
2007-04-04 16:40 ` Linus Torvalds
2007-04-04 16:59 ` Johannes Schindelin
2007-04-04 17:12 ` Linus Torvalds
2007-04-04 17:47 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2007-02-28 13:03 Andy Parkins
2007-02-28 14:44 ` Johannes Schindelin
2007-02-28 14:51 ` Nicolas Pitre
2007-02-28 15:15 ` Andy Parkins
2007-02-28 15:37 ` Johannes Schindelin
2007-02-28 18:42 ` Andy Parkins
2007-02-28 19:41 ` Johannes Schindelin
2007-02-28 15:26 ` Andy Parkins
2007-02-28 18:58 ` Rogan Dawes
2007-02-28 19:42 ` Johannes Schindelin
2007-02-28 21:27 ` Rogan Dawes
2007-03-01 1:09 ` Johannes Schindelin
2007-03-01 6:58 ` Rogan Dawes
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=4613A974.60808@dawes.za.net \
--to=lists@dawes.za.net \
--cc=andyparkins@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 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).