From: Nicolas Pitre <nico@cam.org>
To: Steven Grimm <koreth@midwinter.com>
Cc: John Goerzen <jgoerzen@complete.org>, git@vger.kernel.org
Subject: Re: Rename handling
Date: Mon, 19 Mar 2007 14:35:03 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.83.0703191427140.18328@xanadu.home> (raw)
In-Reply-To: <45FED31B.8070307@midwinter.com>
On Mon, 19 Mar 2007, Steven Grimm wrote:
> So to answer your question, in my opinion if 100% guaranteed renames are high
> on your priority list, then Mercurial might be the better option for now. In
> practice, I've found that git's 99+% rename detection has yet to fail on me
> aside from the above directory renaming case, but at the end of the day it
> *is* guessing at your renames after the fact.
>
> Okay, git gurus, show me no mercy. :)
Well... the fact that you _still_ use GIT even in the face of a 1%
probability that it might guess renames wrong (according to your own
numbers) should mean that you didn't felt switching to Mercurial was
worth the 100% guarantee for rename identification.
And some will argue that explicit renames are susceptible to user error
misidentifying the rename too, certainly in the 1% figure of all renames
if not more.
So maybe, just maybe, at the end of the day getting renames right 100%
of the time instead of 99% is not such a big thing after all.
Nicolas
next prev parent reply other threads:[~2007-03-19 18:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 16:10 Rename handling John Goerzen
2007-03-19 18:14 ` Steven Grimm
2007-03-19 18:35 ` Nicolas Pitre [this message]
2007-03-19 18:48 ` Linus Torvalds
2007-03-19 19:57 ` Steven Grimm
2007-03-19 20:19 ` Martin Langhoff
2007-03-20 8:33 ` Junio C Hamano
2007-03-19 20:22 ` Linus Torvalds
2007-03-19 20:02 ` Robin Rosenberg
2007-03-19 20:34 ` Linus Torvalds
2007-03-19 19:36 ` Steven Grimm
2007-03-19 19:45 ` Steven Grimm
2007-03-19 20:07 ` Linus Torvalds
2007-03-19 20:17 ` Nicolas Pitre
2007-03-19 20:44 ` Daniel Barkalow
2007-03-19 19:03 ` Andy Parkins
2007-03-19 19:21 ` Steven Grimm
2007-03-21 0:06 ` Jakub Narebski
2007-03-21 0:25 ` Johannes Schindelin
2007-03-21 22:28 ` Steven Grimm
2007-03-21 23:01 ` Johannes Schindelin
2007-03-21 23:10 ` Linus Torvalds
2007-03-22 0:10 ` Martin Langhoff
2007-03-22 2:01 ` Jakub Narebski
2007-03-22 2:39 ` Martin Langhoff
2007-03-22 3:32 ` Jakub Narebski
2007-03-22 3:53 ` Linus Torvalds
2007-03-19 19:15 ` Daniel Barkalow
2007-03-19 19:49 ` John Goerzen
2007-03-19 22:27 ` Junio C Hamano
2007-03-21 0:21 ` 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=alpine.LFD.0.83.0703191427140.18328@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=jgoerzen@complete.org \
--cc=koreth@midwinter.com \
/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).