Re: renaming contrib. (was multi-platform, multi-locale regression tests)
От | Tom Lane |
---|---|
Тема | Re: renaming contrib. (was multi-platform, multi-locale regression tests) |
Дата | |
Msg-id | 15712.1289491681@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: renaming contrib. (was multi-platform, multi-locale regression tests) (Marti Raudsepp <marti@juffo.org>) |
Ответы |
Re: renaming contrib. (was multi-platform, multi-locale
regression tests)
|
Список | 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 по дате отправления: