On Tue, 2013-04-16 at 10:19 +0200, Miklos Vajna wrote:
I tried that on a sample repo, so thanks for bringing this up. It seems
the git rename detection is O(N^2), so the default number of renamed
files is limited to avoid long merges.
Presumably it would be possible to cache rename information trawled
from the history at great cost, so a second time a cherry-pick is done,
things are much harder ? (at least locally that is).
ATB,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Context
- Re: minutes of ESC call ... (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.