From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC 0/4] Perl rewrite of Ruby git-related
Date: Mon, 01 Jul 2013 10:00:22 -0700 [thread overview]
Message-ID: <7vobamgqqh.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1372590512-21341-1-git-send-email-sunshine@sunshineco.com> (Eric Sunshine's message of "Sun, 30 Jun 2013 07:08:28 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> In this submission, the command name has changed to git-contacts since
> git-related felt too generic. (git-contacts seemed best of several
> possibilities I surveyed: git-people, git-interested, git-mentioned,
> git-blame-us.)
I admit I am pretty bad at naming, but "contacts" sounds like the
most sensible name for what it wants to do (blame-us sounds cute to
my ears, though ;-).
> No attempt is made to answer Junio's v9 review[5], as I lack sufficient
> insight with '-C' options to be able to respond properly.
I just wanted to see if we want to allow the end user of this script
to specify what -C level they want the underlying blame to use, or
just a hardcoded one should suffice (and if so an explanation why).
> My Perl may be rusty and idiomatic usage may be absent.
That is OK. We need to start somewhere.
Thanks. Folks, please discuss ;-).
next prev parent reply other threads:[~2013-07-01 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 11:08 [PATCH/RFC 0/4] Perl rewrite of Ruby git-related Eric Sunshine
2013-06-30 11:08 ` [PATCH/RFC 1/4] contrib: add git-contacts helper Eric Sunshine
2013-07-01 18:39 ` Junio C Hamano
2013-07-01 19:17 ` Junio C Hamano
2013-07-02 8:17 ` Eric Sunshine
2013-07-02 18:32 ` Junio C Hamano
2013-07-02 19:04 ` Eric Sunshine
2013-06-30 11:08 ` [PATCH/RFC 2/4] contrib: contacts: add support for multiple patches Eric Sunshine
2013-07-01 18:50 ` Junio C Hamano
2013-07-01 18:57 ` Junio C Hamano
2013-07-02 8:52 ` Eric Sunshine
2013-06-30 11:08 ` [PATCH/RFC 3/4] contrib: contacts: add ability to parse from committish Eric Sunshine
2013-06-30 11:08 ` [PATCH/RFC 4/4] contrib: contacts: interpret committish akin to format-patch Eric Sunshine
2013-07-01 17:00 ` Junio C Hamano [this message]
2013-07-02 9:01 ` [PATCH/RFC 0/4] Perl rewrite of Ruby git-related Eric Sunshine
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=7vobamgqqh.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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).