From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] Detect renames in diff family.
Date: Thu, 19 May 2005 16:48:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0505191643030.20274@localhost.localdomain> (raw)
In-Reply-To: <7vy8abx8ay.fsf@assigned-by-dhcp.cox.net>
On Thu, 19 May 2005, Junio C Hamano wrote:
> >>>>> "NP" == Nicolas Pitre <nico@cam.org> writes:
>
> NP> Yes, but 0-9 is putting a bound on the accuracy. What if someone wants
> NP> not more than 2% difference?
>
> That statement is correct, but I think you are looking at it
> from a developer perspective.
>
> I suspect people would not want to pay the price of having
> always to type many digits for the benefit of being able to
> specify differences of 2% and 5%. Would you also complain gzip
> only lets you say -1 .. -9 and not -1.63 ;-)?
Are we talking about git plumbing or porcelain here?
Nicolas
next prev parent reply other threads:[~2005-05-19 20:47 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 10:32 [PATCH] Detect renames in diff family Junio C Hamano
2005-05-19 16:19 ` Linus Torvalds
2005-05-19 17:13 ` Junio C Hamano
2005-05-19 17:31 ` Linus Torvalds
2005-05-19 18:29 ` Nicolas Pitre
2005-05-19 18:46 ` Junio C Hamano
2005-05-19 18:58 ` Nicolas Pitre
2005-05-19 20:36 ` Junio C Hamano
2005-05-19 20:48 ` Nicolas Pitre [this message]
2005-05-19 21:44 ` Junio C Hamano
2005-05-19 22:26 ` Linus Torvalds
2005-05-19 23:32 ` Junio C Hamano
2005-05-20 0:10 ` Linus Torvalds
2005-05-20 0:48 ` Junio C Hamano
2005-05-19 18:47 ` Junio C Hamano
2005-05-19 18:42 ` Junio C Hamano
2005-05-19 18:55 ` Linus Torvalds
2005-05-19 19:53 ` Junio C Hamano
2005-05-19 20:12 ` H. Peter Anvin
2005-05-19 17:46 ` Joel Becker
2005-05-21 9:37 ` Junio C Hamano
2005-05-21 9:39 ` [PATCH 1/3] Diff overhaul, adding half of copy detection Junio C Hamano
2005-05-21 9:40 ` [PATCH 2/3] Introducing software archaeologist's tool "pickaxe" Junio C Hamano
2005-05-21 22:02 ` [PATCH] Constness fix for pickaxe option Junio C Hamano
2005-05-21 22:16 ` Linus Torvalds
2005-05-21 9:42 ` [PATCH 3/3] Diff overhaul, adding the other half of copy detection Junio C Hamano
2005-05-21 10:11 ` [PATCH] Teach diff-tree to report unmodified paths for -C option Junio C Hamano
2005-05-21 10:51 ` Junio C Hamano
2005-05-21 17:25 ` [PATCH 3/3] Diff overhaul, adding the other half of copy detection Linus Torvalds
2005-05-21 18:10 ` [PATCH 3/3] Diff overhaul, adding the other half Junio C Hamano
2005-05-21 18:27 ` Linus Torvalds
2005-05-21 18:34 ` Linus Torvalds
2005-05-21 18:45 ` Linus Torvalds
2005-05-21 20:10 ` Junio C Hamano
2005-05-24 5:37 ` Junio C Hamano
2005-05-24 6:19 ` Linus Torvalds
2005-05-24 8:16 ` Junio C Hamano
2005-05-24 8:31 ` Linus Torvalds
2005-05-24 9:05 ` Junio C Hamano
2005-05-26 3:17 ` [RFC/PATCH] Detect copies harder in diff-tree Junio C Hamano
2005-05-21 19:54 ` [PATCH 3/3] Diff overhaul, adding the other half Junio C Hamano
2005-05-21 22:55 ` [PATCH] Tweak diffcore-rename heuristics Junio C Hamano
[not found] ` <Pine.LNX.4.58.0505211004400.2206@ppc970.osdl.org>
[not found] ` <7v4qcwihu1.fsf@assigned-by-dhcp.cox.net>
2005-05-23 6:50 ` Now I think I am done with diff 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=Pine.LNX.4.62.0505191643030.20274@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).