From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: 100%
Date: Sat, 23 Jun 2007 02:31:28 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706230222330.4059@racer.site> (raw)
In-Reply-To: <86abusi1fw.fsf@lola.quinscape.zz>
Hi,
On Fri, 22 Jun 2007, David Kastrup wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > On Fri, 22 Jun 2007, David Kastrup wrote:
> >
> >> As a note aside: would it be possible to always round downwards when
> >> computing similarities or converting between them?
> >
> > I'd rather not. This would be counterintuitive. People expect rounded
> > values.
>
> Which people?
Me, for one. Thank you very much.
> The people I know will expect "100% identical" or even "100.0%
> identical" to mean identical, period. They will be quite surprised to
> hear that "99.95%" is supposed to be included.
Granted, 100.0% means as close as you can get to "completely" with 4
digits. But if you have an integer, you better use the complete range,
rather than arbitrarily make one number more important than others.
For if you see an integer, you usually assume a rounded value. If you
don't, you're hopeless.
> Also, for any kind of decision made upon percentages, it is much more
> relevant to be able to draw a line at 50% rather than at 49.5%.
I do see too many people in my day job who take the numbers they see for
absolute truths, so I cannot take that statement seriously, sorry.
> Could you name a _single_ use case where rounding down could cause an
> actual problem or even inconvenience for people?
Could you name a _single_ use case where it does not?
I mean, honestly, really. Really, really, really. A number is only a weak
_indicator_, and an integer even more so, for what is _really_ going on.
> >> I very much would like to see the 100% figure reserved for identity.
> >> This is particularly relevant when interpreting the output of
> >> git-diff --name-status with regard to R100, C100 and similar flags.
> >
> > You should never depend on the output of --name-status if you're
> > interested in identifying identical files, but on the object names.
>
> Which is rather inconvenient.
Frankly, I am getting bored.
This argument crops up ever so often. "If you did that, _I_ could be more
lazy, and the _hell_ with other people who expect otherwise!".
No, really.
> I _know_ that one can't rely on the output of --name-status right now.
And I _know_ that you can't rely on integer numbers. Or _any_ number which
is not _completely_ precise.
Really, I am getting bored with this discussion.
Ciao,
Dscho
next prev parent reply other threads:[~2007-06-23 1:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 3:06 Basename matching during rename/copy detection Shawn O. Pearce
2007-06-21 3:13 ` Junio C Hamano
2007-06-21 8:00 ` Andy Parkins
2007-06-21 8:07 ` Junio C Hamano
2007-06-21 9:50 ` Andy Parkins
2007-06-21 11:52 ` Johannes Schindelin
2007-06-21 12:44 ` Andy Parkins
2007-06-21 12:53 ` Matthieu Moy
2007-06-21 13:10 ` Jeff King
2007-06-21 13:18 ` Johannes Schindelin
2007-06-21 13:25 ` Matthieu Moy
2007-06-21 13:52 ` Johannes Schindelin
2007-06-21 15:37 ` Steven Grimm
2007-06-21 15:53 ` Johannes Schindelin
2007-06-21 16:57 ` Steven Grimm
2007-06-21 13:22 ` Johannes Schindelin
2007-06-21 3:42 ` Linus Torvalds
2007-06-21 11:52 ` [PATCH] diffcore-rename: favour identical basenames Johannes Schindelin
2007-06-21 13:19 ` Jeff King
2007-06-21 14:03 ` Johannes Schindelin
2007-06-21 16:20 ` Linus Torvalds
2007-06-21 17:52 ` Junio C Hamano
2007-06-21 18:24 ` Linus Torvalds
2007-06-22 15:19 ` Andy Parkins
2007-06-22 15:28 ` Johannes Schindelin
2007-06-22 17:51 ` Aidan Van Dyk
2007-06-22 1:14 ` Johannes Schindelin
2007-06-22 5:41 ` Jeff King
2007-06-22 10:22 ` Johannes Schindelin
2007-06-22 7:17 ` Johannes Sixt
2007-06-22 10:39 ` Johannes Schindelin
2007-06-22 10:52 ` 100% (was: [PATCH] diffcore-rename: favour identical basenames) David Kastrup
2007-06-22 12:49 ` Johannes Schindelin
[not found] ` <86abusi1fw.fsf@lola.quinscape.zz>
2007-06-23 1:31 ` Johannes Schindelin [this message]
2007-06-23 10:18 ` 100% René Scharfe
2007-06-23 10:56 ` 100% Johannes Schindelin
2007-06-23 11:41 ` 100% René Scharfe
2007-06-23 12:00 ` 100% Johannes Schindelin
2007-06-23 12:11 ` 100% René Scharfe
2007-06-23 12:21 ` 100% Johannes Schindelin
2007-06-24 22:23 ` 100% René Scharfe
2007-06-23 19:33 ` 100% Junio C Hamano
2007-06-23 20:41 ` 100% Johannes Schindelin
2007-06-23 5:44 ` [PATCH] diffcore-rename: favour identical basenames 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.64.0706230222330.4059@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=dak@gnu.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;
as well as URLs for NNTP newsgroup(s).