From: Sam Vilain <sam@vilain•net>
To: Steven Grimm <koreth@midwinter•com>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: Directory renames (was Re: blame follows renames, but log doesn't)
Date: Thu, 21 Jun 2007 08:18:22 +1200 [thread overview]
Message-ID: <46798B8E.6040103@vilain.net> (raw)
In-Reply-To: <4678204C.6050409@midwinter.com>
Steven Grimm wrote:
> Hope that's illuminating or at least interesting to someone.
I didn't review your test cases in detail, but they seemed to suffer
from what I call "over-trivialization"; the heuristic methods don't work
very well for these non-real-world test cases because they're not long
enough. Are you confident that these deficiencies are still there with
longer examples?
Sam.
next prev parent reply other threads:[~2007-06-20 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 1:10 blame follows renames, but log doesn't Martin Langhoff
2007-06-19 1:34 ` Sam Vilain
2007-06-19 7:19 ` Theodore Tso
2007-06-19 8:31 ` Martin Langhoff
2007-06-19 8:39 ` Junio C Hamano
2007-06-19 9:54 ` Steven Grimm
2007-06-19 18:28 ` Directory renames (was Re: blame follows renames, but log doesn't) Steven Grimm
2007-06-20 20:18 ` Sam Vilain [this message]
2007-06-20 20:59 ` Steven Grimm
2007-06-20 22:11 ` blame follows renames, but log doesn't Jakub Narebski
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=46798B8E.6040103@vilain.net \
--to=sam@vilain$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=koreth@midwinter$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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