Re: [PATCH 1/3] doc: clarify documentation for rename/copy limits

From: Elijah Newren <newren@gmail.com>
Date: Jul 11, 2021, 04:52 UTC
Message-ID: <CABPp-BGQtYeRtK77=7fn7xJPPYV9h=duroTw1tQqbz-9-BXP=A@mail.gmail.com>
In-Reply-To: <450310cd-7b01-58f5-1f74-739d61db97fa@gmail.com>

On Sat, Jul 10, 2021 at 9:37 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:

Show 17 quoted lines

>
> On 11/07/21 07.46, Elijah Newren via GitGitGadget wrote:
> >   -l<num>::
> > -     The `-M` and `-C` options require O(n^2) processing time where n
> > -     is the number of potential rename/copy targets.  This
> > -     option prevents rename/copy detection from running if
> > -     the number of rename/copy targets exceeds the specified
> > -     number.
> > +     The `-M` and `-C` options can require O(n^2) processing time
> > +     where n is the number of potential rename/copy targets.  This
> > +     option prevents the quadratic portion of rename/copy detection
> > +     from running if the number of rename/copy targets exceeds the
> > +     specified number.  Defaults to diff.renameLimit, or if that is
> > +     also unspecified, to 400.
>
> Why not just defaults to diff.renameLimit if the default for it and -l
> are both 400?

Good point; I'll make that change and include it in the next re-roll.