From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH v2 1/8] Add new git-cc-cmd helper to contrib
Date: Fri, 19 Apr 2013 22:05:27 +0200 [thread overview]
Message-ID: <5171A387.808@kdbg.org> (raw)
In-Reply-To: <7v8v4e1fyz.fsf@alter.siamese.dyndns.org>
Am 19.04.2013 21:24, schrieb Junio C Hamano:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> On Fri, Apr 19, 2013 at 12:08 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>>> The code finds the changes of a commit, runs 'git blame' for each chunk
>>>> to see which other commits are relevant, and then reports the author and
>>>> signers.
>
> But I think it can be useful outside the context of send-email as
> well, and having one independent tool that does one single job well
> is a better design. Perhaps it is better to name it less specific
> to send-email's cc-cmd option. "git people"? "git whom"? "git
> reviewers"? I dunno, but along those lines.
Would it make sense to integrate this in git shortlog, which already
does something similar?
-- Hannes
next prev parent reply other threads:[~2013-04-19 20:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 5:14 [PATCH v2 0/8] New git-cc-cmd helper Felipe Contreras
2013-04-19 5:14 ` [PATCH v2 1/8] Add new git-cc-cmd helper to contrib Felipe Contreras
2013-04-19 13:26 ` Ramkumar Ramachandra
2013-04-19 16:30 ` Felipe Contreras
2013-04-19 17:08 ` Junio C Hamano
2013-04-19 17:35 ` Felipe Contreras
2013-04-19 19:24 ` Junio C Hamano
2013-04-19 19:35 ` Felipe Contreras
2013-04-19 19:56 ` Junio C Hamano
2013-04-19 20:05 ` Johannes Sixt [this message]
2013-04-20 20:22 ` Junio C Hamano
2013-04-22 7:30 ` Jeremy Rosen
2013-04-19 20:08 ` Junio C Hamano
2013-04-19 5:14 ` [PATCH v2 2/8] contrib: cc-cmd: add option parsing Felipe Contreras
2013-04-19 5:14 ` [PATCH v2 3/8] contrib: cc-cmd: add support for multiple patches Felipe Contreras
2013-04-19 5:14 ` [PATCH v2 4/8] contrib: cc-cmd: add option to show commits Felipe Contreras
2013-04-19 5:14 ` [PATCH v2 5/8] contrib: cc-cmd: add option to parse from committish Felipe Contreras
2013-04-19 17:59 ` Junio C Hamano
2013-04-19 18:29 ` Felipe Contreras
2013-04-19 5:14 ` [PATCH v2 6/8] contrib: cc-cmd: parse committish like format-patch Felipe Contreras
2013-04-19 5:14 ` [PATCH v2 7/8] contrib: cc-cmd: fix parsing of rev-list args Felipe Contreras
2013-04-19 5:14 ` [PATCH v2 8/8] contrib: cc-cmd: add option to fetch aliases 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=5171A387.808@kdbg.org \
--to=j6t@kdbg.org \
--cc=artagnon@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).