Re: [PATCH v6] Add git-grep threads param

This version seems to break t7811 when applied on top of 37023ba3 (Seventh batch for 2.7, 2015-10-26). I'll eject it from 'pu' for today's integration. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at

RE: [PATCH v6] Add git-grep threads param

Hello all, does anybody have time to review this patch? PS Sorry for bothering =) -- Best Regards, Victor From: Victor Leschuk [vlesc...@gmail.com] Sent: Wednesday, November 11, 2015 03:52 To: git@vger.kernel.org Cc: Victor Leschuk Subject: [PATCH v6]

Re: [PATCH v6] Add git-grep threads param

On Mon, Nov 16, 2015 at 8:11 AM, Victor Leschuk wrote: > "git grep" can now be configured (or told from the command line) > how many threads to use when searching in the working tree files. > > Changes to default behavior: number of threads now doesn't depend > on

Re: [PATCH v6] Add git-grep threads param

On Wed, Nov 11, 2015 at 12:52 PM, Victor Leschuk wrote: > "git grep" can now be configured (or told from the command line) > how many threads to use when searching in the working tree files. > > Changes to default behavior: number of threads now doesn't depend > on

Re: [PATCH v6] Add git-grep threads param

I forgot.. On Wed, Nov 11, 2015 at 12:52 PM, Victor Leschuk wrote: > + else if (num_threads < 0) > + die("Invalid number of threads specified (%d)", num_threads); Please wrap this string with _() so it can be translated -- Duy -- To unsubscribe from this

Re: [PATCH v6] Add git-grep threads param

On Mon, Nov 16, 2015 at 05:11:16AM -0800, Victor Leschuk wrote: > The earlier version of this patch is already included in /pu branch, > however as we all agreed ($gmane/280299) we have changed the default > behavior and the meaning of "0". The question is: what is the right > way to include

RE: [PATCH v6] Add git-grep threads param

Hello all, The earlier version of this patch is already included in /pu branch, however as we all agreed ($gmane/280299) we have changed the default behavior and the meaning of "0". The question is: what is the right way to include changes from patch v6 (this one) into already merged patch to