git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Subject: cache for copy/rename detection
Date: Sun, 26 Nov 2006 19:59:31 +0700	[thread overview]
Message-ID: <fcaeb9bf0611260459t7afa68eerf4dc66d7eb7fdcc1@mail.gmail.com> (raw)

I thought about this lately. git's expensive copy/rename detection can
be run once and the results are kept somewhere in .git. Copy/rename
detection depends on tree objects and git detection algorithm. Tree
objects are immutable and git algorithm change rate is low IMO. So
cache invalidation is unlikely to happen.

Another thing I want to do with this cache is ability to manually
inject some hints to git. For example, I remove a file. Several
commits later, I revive that file in another place. I know that two
files are the same but can't tell git (and I don't think Git will
detect this pattern). With this cache, I can tell git this file is a
copy of that file.

What do you think?
-- 

                 reply	other threads:[~2006-11-26 12:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=fcaeb9bf0611260459t7afa68eerf4dc66d7eb7fdcc1@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.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).