Re: renaming contrib. (was multi-platform, multi-locale regression tests) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: renaming contrib. (was multi-platform, multi-locale regression tests)
Date
Msg-id 15712.1289491681@sss.pgh.pa.us
Whole thread Raw
In response to Re: renaming contrib. (was multi-platform, multi-locale regression tests)  (Marti Raudsepp <marti@juffo.org>)
Responses Re: renaming contrib. (was multi-platform, multi-locale regression tests)
List pgsql-hackers
Marti Raudsepp <marti@juffo.org> writes:
> On Thu, Nov 11, 2010 at 17:24, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Given that we have, in fact, never renamed any files in the history of
>> the project, I'm wondering exactly why it thinks that the number of
>> potential rename/copy targets isn't zero.

> Because git doesn't do "rename tracking" at all -- a rename operation
> is no different from a delete+add operation. Instead it tracks how
> lines of code move around in the tree:
> https://git.wiki.kernel.org/index.php/GitFaq#Why_does_git_not_.22track.22_renames.3F

Hmmm ... so rename tracking is O(N^2) in the total number of patches
applied, or lines patched, or some such measure, between the branches
you're trying to patch between?  Ugh.  Doesn't sound like something
we want to grow dependent on.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: renaming contrib. (was multi-platform, multi-locale regression tests)
Next
From: Andrew Dunstan
Date:
Subject: Re: renaming contrib. (was multi-platform, multi-locale regression tests)