git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Fredrik Kuivinen <freku045@student.liu.se>,
	git@vger.kernel.org
Subject: Re: Moved files and merges
Date: Mon, 05 Sep 2005 09:37:42 -0700	[thread overview]
Message-ID: <431C7456.80907@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509050825170.3568@evo.osdl.org>

Linus Torvalds wrote:
> 
> It's a totally broken model. Really.
> 
> You think it solves issues, but it just creates more bugs and problems 
> than it solves.
> 
> Trust me. The whole point of git is that "content is the only thing that 
> matters", and that there isn't any other meta-data. If you break that 
> fundamental assumption, everything git does so well will break. 
> 
> I think we've already shown that the "content matters" approach works.  I
> claim that the git rename tracking works better than any other SCM out 
> there, _exactly_ because it doesn't make the mistake of trying to track 
> anything but content.
> 
> The "moved + modified files" is not anything special. The current 
> automatic merger may not handle it, but that's not because it _can't_ 
> handle it, it's because it tries to be simple and efficient. 
> 
> And because it's so _incredibly_ fast for all the normal cases, you can 
> now spend some effort on figuring out renames dynamically for the few 
> cases where it fails. Does it do so now? No. Would adding UUID's help? 
> Hell no. It would be just an unmitigated disaster.
> 

Okay, how about keeping a cache (derived from the contents) of these 
types of data, to assist the merge if necessary?  If it doesn't exist 
when needed, it can just be created, which may take O(n) time.

	-hpa

  reply	other threads:[~2005-09-05 16:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02 23:59 Moved files and merges H. Peter Anvin
2005-09-03  0:20 ` Martin Langhoff
2005-09-04  4:14   ` H. Peter Anvin
2005-09-03  1:36 ` Junio C Hamano
2005-09-03  8:25   ` Junio C Hamano
2005-09-03 18:06     ` Fredrik Kuivinen
2005-09-03 18:53       ` Junio C Hamano
2005-09-03 18:46     ` Junio C Hamano
2005-09-03 19:05       ` Sam Ravnborg
2005-09-03 19:32         ` Junio C Hamano
2005-09-03 22:03           ` Sam Ravnborg
2005-09-04  7:32             ` Junio C Hamano
2005-09-04 18:28               ` Daniel Barkalow
2005-09-04 19:10                 ` Junio C Hamano
2005-09-05 15:16                   ` H. Peter Anvin
2005-09-05 15:47                     ` Linus Torvalds
2005-09-05 16:37                       ` H. Peter Anvin [this message]
2005-09-05 18:08                       ` Junio C Hamano
2005-09-05 18:33                     ` Junio C Hamano
2005-09-05 18:43                       ` H. Peter Anvin
2005-09-04  8:27             ` Junio C Hamano
2005-09-03 19:21       ` Fredrik Kuivinen
2005-09-03 18:59     ` Sam Ravnborg

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=431C7456.80907@zytor.com \
    --to=hpa@zytor.com \
    --cc=barkalow@iabervon.org \
    --cc=freku045@student.liu.se \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=sam@ravnborg.org \
    --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).