From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nicolas Pitre <nico@cam.org>, Steven Grimm <koreth@midwinter.com>,
John Goerzen <jgoerzen@complete.org>,
git@vger.kernel.org
Subject: Re: Rename handling
Date: Mon, 19 Mar 2007 21:02:19 +0100 [thread overview]
Message-ID: <200703192102.20258.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703191145530.6730@woody.linux-foundation.org>
måndag 19 mars 2007 19:48 skrev Linus Torvalds:
>
> On Mon, 19 Mar 2007, Nicolas Pitre wrote:
> >
> > 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.
>
> It's much worse than that. I will *guarantee* that renames are missed when
> they come in as traditional patches, for example. That's a 100% error rate
> right there, not some "1%" one.
>
> And even if people never make mistakes, and people *only* use the native
> SCM "rename" functions, I guarantee that the downsides of thinking that
> files have identities is still much much bigger than the upsides. We've
> already shown that the git "blame" functionality is strictly more powerful
> than anything based on renames.
>
> So learn to love the bomb. Rename tracking is *wrong*.
>
> Linus
How about this simple receipe for defeating rename tracking (real world):
User needs to modify A. User renames A to OLD_A within his/her IDE. SCM
records the rename. User now uses SaveAs to restore A, and SCM detects the
*NEW* file A.
-- robin
next prev parent reply other threads:[~2007-03-19 20:00 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
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 [this message]
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=200703192102.20258.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=jgoerzen@complete.org \
--cc=koreth@midwinter.com \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.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).