From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Grimm <koreth@midwinter.com>
Cc: Nicolas Pitre <nico@cam.org>,
John Goerzen <jgoerzen@complete.org>,
git@vger.kernel.org
Subject: Re: Rename handling
Date: Mon, 19 Mar 2007 13:07:45 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703191259420.6730@woody.linux-foundation.org> (raw)
In-Reply-To: <45FEE869.3040308@midwinter.com>
On Mon, 19 Mar 2007, Steven Grimm wrote:
>
> Err, then I am *going* to consider it a failure of the tool.
Sure.
And then realize that nothing is perfect.
Git is just *closer* to perfect than any other SCM out there. That doesn't
mean that you can never find cases where you consider it failed. It just
means that it fails less than the alternatives.
To be perfect, an SCM would have to be able to infer a higher meaning. Who
knows - maybe that will happen in a few centuries (or decades, but AI has
not had a good track-record so far).
Git tracks exactly the stuff that does *not* require it to infer higher
meanings - purely data. I personally consider it one of gits greatest
strengths: it never matters *how* you get to some state, or what tools you
used (patches, imports from other SCM's, "git mv" with intelligent
developers, "git mv" with total clutzes, "plain mv", random monkeys
typing, whatever). Git tracks not "intent", but "hard data".
The fact that git then can use that unambiguous hard data to show you
interesting patterns is a big deal. But you need to realize that it's an
even *bigger* deal that git only traffics in hard data that leaves
absolutely no room for mistakes.
Git simply doesn't *care* whether you applied a patch to create the
rename, or whether you imported the series from a system that doesn't
track renames, or whether you just forgot to do "git mv". You should be
really really happy about that.
Btw, the reason -M isn't on by default is not that it's more expensive in
CPU-time (it is, but quite frankly, you will never really see that effect
in practice). No, the real reason is that if you use "-M" and actually see
renames, traditional tools no longer understand the patches. And sadly,
there are still too many unwashed and ignorant people out there to make
the default patch format be git-specific.
When the revolution comes, and we can shoot everybody who uses anything
else, we'll turn -M on by default. Don't despair, comrade!
Linus
next prev parent reply other threads:[~2007-03-19 20:10 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
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 [this message]
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=Pine.LNX.4.64.0703191259420.6730@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=jgoerzen@complete.org \
--cc=koreth@midwinter.com \
--cc=nico@cam.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).