From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@osdl.org>,
Fredrik Kuivinen <freku045@student.liu.se>,
git@vger.kernel.org
Subject: Re: Moved files and merges
Date: Mon, 05 Sep 2005 11:43:00 -0700 [thread overview]
Message-ID: <431C91B4.6040609@zytor.com> (raw)
In-Reply-To: <7v4q8z5pqv.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>
> But previous argument by Linus made in a distant (in git
> timescale) past is now ingrained in my brain: "the additional
> metadata" recorded at the commit time can only help us what we
> envisioned in the past when the tool to record that metadata was
> written. If we try to "track" by contents, we can do at least
> the same (diff -M being able to tell renames is an example that
> we can get away without having a UUID) and possibly better,
> depending on how much effort we are willing to spend "drilling
> down" when we actually need to know what happened at merge
> time. What I found most important in that argument by Linus is
> that the "drilling down" algorithm can improve over time while
> "the additional metadata" specification is cast in stone when a
> commit is made.
>
... unless the "additional metadata" is merely a cache, derived from the
contents. The advantage, of course, is that you can produce data that
is more expensive that way. On the other hand, if you don't need it,
it's pointless.
-hpa
next prev parent reply other threads:[~2005-09-05 18:43 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
2005-09-05 18:08 ` Junio C Hamano
2005-09-05 18:33 ` Junio C Hamano
2005-09-05 18:43 ` H. Peter Anvin [this message]
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=431C91B4.6040609@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).