From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, mj@ucw.cz
Subject: Re: [PATCH 3/4] diff --stat: report chmoded binary files like text files
Date: Tue, 01 May 2012 21:39:14 +0200 [thread overview]
Message-ID: <4FA03BE2.2030107@in.waw.pl> (raw)
In-Reply-To: <7vvckf92pp.fsf@alter.siamese.dyndns.org>
On 05/01/2012 08:27 PM, Junio C Hamano wrote:
> Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> writes:
>
>> Binary files chmoded without content change were reported as if they
>> were rewritten. At the same time, text files in the same situation
>> were reported as "unchanged". Let's treat binary files like text files
>> here, and simply say that they are unchanged.
>>
>> For text files, we knew that they were unchanged if the numbers of
>> lines added and deleted were both 0. For binary files this metric does
>> not make sense and is not calculated, so a new way of conveying this
>> information is needed. A new flag is_unchanged is added in struct
>> diffstat_t that is set if the contents of both files are identical.
>> For consistency, this new flag is used both for text files and binary
>> files.
>>
>> Output of --shortstat is modified in the same way.
>>
>> Reported-by: Martin Mareš <mj@ucw.cz>
>> Signed-off-by: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
>> ---
>> diff.c | 28 +++++++++++++++++-----------
>> t/t4006-diff-mode.sh | 8 +-------
>> 2 files changed, 18 insertions(+), 18 deletions(-)
>>
>> diff --git a/diff.c b/diff.c
>> index 7da16c9..6eb2946 100644
>> --- a/diff.c
>> +++ b/diff.c
>> @@ -1299,6 +1299,7 @@ struct diffstat_t {
>> unsigned is_unmerged:1;
>> unsigned is_binary:1;
>> unsigned is_renamed:1;
>> + unsigned is_unchanged:1;
>
> The name is somewhat misleading, as a filepair that consists of two blobs
> with the same contents with different mode bits is still "changed", and
> you are trying to say that they have the same contents.
>
>> @@ -1471,7 +1472,7 @@ static void show_stats(struct diffstat_t *data, struct diff_options *options)
>> struct diffstat_file *file = data->files[i];
>> uintmax_t change = file->added + file->deleted;
>> if (!data->files[i]->is_renamed &&
>> - (change == 0)) {
>> + data->files[i]->is_unchanged) {
>
> I am not sure if all these hunks are needed. If you are going to show
> only " Bin\n" for a filepair with the same binary contents, perhaps it is
> simpler to set added/deleted fields of such a filepair to 0? Then most of
> the hunks in this patch can disappear, no?
>
>> @@ -2379,6 +2383,8 @@ static void builtin_diffstat(const char *name_a, const char *name_b,
>> return;
>> }
>>
>> + data->is_unchanged = hashcmp(one->sha1, two->sha1) == 0;
>
> Please write it as "!hashcmp(a, b)", not "hashcmp(a, b) == 0".
>
> In any case, how about doing it like this instead?
Yeah, this is much nicer.
On top of this, 4/4 becomes:
- else {
+ else if (hashcmp(one->sha1, two->sha1)) {
and the time improvement is the same (0.8 vs 2.0 s).
Do you want me to resend with your replacement patch?
Zbyszek
next prev parent reply other threads:[~2012-05-01 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 17:10 [PATCH 0/4] report chmod'ed binary files the same as text files Zbigniew Jędrzejewski-Szmek
2012-05-01 17:10 ` [PATCH 1/4] test: modernize style of t4006 Zbigniew Jędrzejewski-Szmek
2012-05-01 18:00 ` Junio C Hamano
2012-05-01 19:55 ` Zbigniew Jędrzejewski-Szmek
2012-05-01 17:10 ` [PATCH 2/4] tests: check --[short]stat output after chmod Zbigniew Jędrzejewski-Szmek
2012-05-02 7:36 ` Johannes Sixt
2012-05-01 17:10 ` [PATCH 3/4] diff --stat: report chmoded binary files like text files Zbigniew Jędrzejewski-Szmek
2012-05-01 18:27 ` Junio C Hamano
2012-05-01 19:39 ` Zbigniew Jędrzejewski-Szmek [this message]
2012-05-01 17:10 ` [PATCH 4/4] diff --stat: do not run diff on indentical files Zbigniew Jędrzejewski-Szmek
2012-05-03 11:45 ` [PATCH 0/4] report chmod'ed binary files the same as text files Martin Mares
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=4FA03BE2.2030107@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mj@ucw.cz \
/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).