git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: problem with git detecting proper renames
Date: Fri, 30 Nov 2007 01:21:32 +0100	[thread overview]
Message-ID: <finl2d$9rk$1@ger.gmane.org> (raw)
In-Reply-To: alpine.LFD.0.9999.0711290934260.8458@woody.linux-foundation.org

Linus Torvalds wrote:
> On Thu, 29 Nov 2007, Kumar Gala wrote:
>> 
>> I did some git-mv and got the following:
>> 
>> the problem is git seems confused about what file was associated with its
>> source.
> 
> Well, I wouldn't say "confused". It found multiple identical options for 
> the source, and picked the first one (where "first one" may not be obvious 
> to a human, it can depend on an internal hash order).

By the way, which git version do you use? IIRC we have improved rename
detection heuristics to take into account similarity of filenames when
contents is identical...

...ah, I see, it is git 1.5.3.4

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

      parent reply	other threads:[~2007-11-30  0:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 16:57 problem with git detecting proper renames Kumar Gala
2007-11-29 17:44 ` Linus Torvalds
2007-11-29 19:06   ` Kumar Gala
2007-11-29 19:27     ` Linus Torvalds
2007-11-29 19:32       ` Kumar Gala
2007-11-29 20:27       ` Kumar Gala
2007-11-29 21:30         ` Fix a pathological case in " Linus Torvalds
2007-11-29 23:03           ` Linus Torvalds
2007-11-29 23:52             ` Jeff King
2007-11-30  0:41               ` Linus Torvalds
2007-11-30  0:48                 ` Jeff King
2007-11-30  1:18                 ` Kumar Gala
2007-11-30  0:40             ` Junio C Hamano
2007-11-30  0:21   ` Jakub Narebski [this message]

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='finl2d$9rk$1@ger.gmane.org' \
    --to=jnareb@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).