Git development
 help / color / mirror / Atom feed
From: Cristian Tibirna <tibirna@kde.org>
To: git@vger.kernel.org
Subject: git diff-tree -r -C output inexact sometimes
Date: Thu, 20 Sep 2012 23:20:31 -0400	[thread overview]
Message-ID: <2789023.yr3ihcVOhq@leto> (raw)

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

Hello

A colleague of mine discovered an inconsistency in the functioning of 

git diff-tree -r -C

in specific conditions. As tenuous as these conditions might seem (once you 
run the script in attachment and analyse its output), please rest assured that 
it comes from a real-life case.

Running the script in attachment produces a git repository in which were 
operated a large number of file renames, in which many of the renamed files 
(in this particular case all) have the same content but different names.

The commit data from the renaming operation (last commit in the script-
generated history) is inexactly rendered by the command 

git diff-tree -r -C master

The logical result is correctly produced by the more restricted command

git diff-tree -r -M master

IMO for this particular last commit both the above commands should return the 
same result.

Note that reducing i or j in the generator script attached below makes the bug 
dissapear.

Thanks a lot for your attention.

-- 
Cristian Tibirna
KDE developer .. tibirna@kde.org .. http://www.kde.org

[-- Attachment #2: generate_git_tree.sh --]
[-- Type: application/x-shellscript, Size: 418 bytes --]

             reply	other threads:[~2012-09-21  4:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  3:20 Cristian Tibirna [this message]
2012-09-21  6:03 ` git diff-tree -r -C output inexact sometimes Jeff King

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=2789023.yr3ihcVOhq@leto \
    --to=tibirna@kde.org \
    --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