On Wed, 2014-07-16 at 00:35 -0400, Pranith Kumar wrote:
> The problem is with the default which is at 50% now. That means that a
> commit needs to have changed a file by more than 50% -and- moved it in
> the same commit. This is highly discouraged and unlikely to happen in
> our case.
>
> Even if
On Wed, Jul 16, 2014 at 12:08 AM, Joe Perches wrote:
> On Tue, 2014-07-15 at 22:23 -0400, Pranith Kumar wrote:
>> ping?
>>
>> On Sat, Jul 12, 2014 at 3:25 PM, Pranith Kumar wrote:
>> > get_maintainer tries to follow files with a matching threshold of default
>> > 50%.
>> > This is not really nec
On Tue, 2014-07-15 at 22:23 -0400, Pranith Kumar wrote:
> ping?
>
> On Sat, Jul 12, 2014 at 3:25 PM, Pranith Kumar wrote:
> > get_maintainer tries to follow files with a matching threshold of default
> > 50%.
> > This is not really necessary as we do not change a file and move it in the
> > sam
ping?
On Sat, Jul 12, 2014 at 3:25 PM, Pranith Kumar wrote:
> get_maintainer tries to follow files with a matching threshold of default 50%.
> This is not really necessary as we do not change a file and move it in the
> same
> commit usually. Increasing the threshold to 90% should be sufficient.
get_maintainer tries to follow files with a matching threshold of default 50%.
This is not really necessary as we do not change a file and move it in the same
commit usually. Increasing the threshold to 90% should be sufficient.
I encountered this on a recent commit where I was touching 12 files.
5 matches
Mail list logo
