From: Rogan Dawes <discard@dawes.za.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] Show binary file size change in diff --stat
Date: Wed, 28 Feb 2007 20:58:31 +0200 [thread overview]
Message-ID: <45E5D0D7.5070305@dawes.za.net> (raw)
In-Reply-To: <200702281303.11951.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 +123456B -12345B
>
> The "+" item is the size of the new version, the "-" item is the size of
> the old version. 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 "B" (for bytes) is shown to highlight the fact that these numbers
> are not "number of lines", but actual bytes.
>
> 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.
How about showing the size of the changes between the 2 files via the
libxdiff binary patch function?
It would probably not be that difficult to generate a binary patch, and
then derive some stats from it.
Rogan
next prev parent reply other threads:[~2007-02-28 18:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 13:03 [PATCH] Show binary file size change in diff --stat 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-04-04 13:14 Andy Parkins
2007-04-04 13:34 ` Rogan Dawes
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
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=45E5D0D7.5070305@dawes.za.net \
--to=discard@dawes.za.net \
--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).