On Fri, Apr 26, 2013 at 10:01 PM, Ramkumar Ramachandra
wrote:
> Felipe Contreras wrote:
>> That's fine, I was mostly asking Ramkumar who earlier argued earlier
>> versions of this patch were not understandable.
>
> Sorry, still catching up with list emails. At a glance, part 1 looks
> much better
Felipe Contreras wrote:
> That's fine, I was mostly asking Ramkumar who earlier argued earlier
> versions of this patch were not understandable.
Sorry, still catching up with list emails. At a glance, part 1 looks
much better. Will read through more carefully soon.
Thanks.
--
To unsubscribe fro
On Fri, Apr 26, 2013 at 6:01 PM, Junio C Hamano wrote:
> Felipe Contreras writes:
>
>> On Thu, Apr 25, 2013 at 2:59 PM, Felipe Contreras
>> wrote:
>>> This script find people that might be interested in a patch, by going
>>> back through the history for each single hunk modified, and finding
>>>
Felipe Contreras writes:
> On Thu, Apr 25, 2013 at 2:59 PM, Felipe Contreras
> wrote:
>> This script find people that might be interested in a patch, by going
>> back through the history for each single hunk modified, and finding
>> people that reviewed, acknowledge, signed, or authored the code
Hi,
On Thu, Apr 25, 2013 at 2:59 PM, Felipe Contreras
wrote:
> This script find people that might be interested in a patch, by going
> back through the history for each single hunk modified, and finding
> people that reviewed, acknowledge, signed, or authored the code the
> patch is modifying.
>
This script find people that might be interested in a patch, by going
back through the history for each single hunk modified, and finding
people that reviewed, acknowledge, signed, or authored the code the
patch is modifying.
It does this by running 'git blame' incrementally on each hunk, and then
6 matches
Mail list logo
