From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>,
Duy Nguyen <pclouds@gmail.com>
Subject: Re: [PATCH v4 01/11] Add new git-related helper to contrib
Date: Fri, 26 Apr 2013 18:23:33 -0500 [thread overview]
Message-ID: <CAMP44s0XnEJWjzU-g=Gq2jJQu-9MJ8S84fAd-7bdomKWEeTCtw@mail.gmail.com> (raw)
In-Reply-To: <7vhaisvqvl.fsf@alter.siamese.dyndns.org>
On Fri, Apr 26, 2013 at 6:01 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> On Thu, Apr 25, 2013 at 2:59 PM, Felipe Contreras
>> <felipe.contreras@gmail.com> 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.
>>>
>>> It does this by running 'git blame' incrementally on each hunk, and then
>>> parsing the commit message. After gathering all the relevant people, it
>>> groups them to show what exactly was their role when the participated in
>>> the development of the relevant commit, and on how many relevant commits
>>> they participated. They are only displayed if they pass a minimum
>>> threshold of participation.
>>
>> Is this patch still not understandable?
>
> Among the people who review patches here and give usable feedback,
> earlier this week Peff said he is away from his mailbox for the rest
> of the week, and I am not reviewing any new topics that are not in
> 'next', being busy in preparation for -rc0, so I wouldn't be able to
> answer that question.
>
> I do not know about the others, but it is understandable from time
> to time there is a period a series is not being reviewed by anybody.
That's fine, I was mostly asking Ramkumar who earlier argued earlier
versions of this patch were not understandable.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2013-04-26 23:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 19:59 [PATCH v4 00/11] Add new git-related helper to contrib Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 01/11] " Felipe Contreras
2013-04-26 22:52 ` Felipe Contreras
2013-04-26 23:01 ` Junio C Hamano
2013-04-26 23:23 ` Felipe Contreras [this message]
2013-04-27 3:01 ` Ramkumar Ramachandra
2013-05-13 23:17 ` Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 02/11] contrib: related: add option parsing Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 03/11] contrib: related: add support for multiple patches Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 04/11] contrib: related: add option to show commits Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 05/11] contrib: related: add option to parse from committish Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 06/11] contrib: related: parse committish like format-patch Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 07/11] contrib: related: fix parsing of rev-list args Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 08/11] contrib: related: support multiple roles Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 09/11] contrib: related: sort by participation Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 10/11] contrib: related: group persons with same email Felipe Contreras
2013-04-25 19:59 ` [PATCH v4 11/11] contrib: related: add support for mailmap Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMP44s0XnEJWjzU-g=Gq2jJQu-9MJ8S84fAd-7bdomKWEeTCtw@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).