From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2013, #07; Sun, 21)
Date: Mon, 22 Jul 2013 03:15:53 -0400 [thread overview]
Message-ID: <CAPig+cQFpddEgkBWYb7fUtijPHCPhtjDu_=wd4br3+qXqLemjg@mail.gmail.com> (raw)
In-Reply-To: <7vy58zozdk.fsf@alter.siamese.dyndns.org>
On Mon, Jul 22, 2013 at 2:57 AM, Junio C Hamano <gitster@pobox.com> wrote:
> * es/contacts (2013-07-21) 5 commits
> - contrib: contacts: add documentation
> - contrib: contacts: add mailmap support
> - contrib: contacts: interpret committish akin to format-patch
> - contrib: contacts: add ability to parse from committish
> - contrib: add git-contacts helper
> (this branch uses es/check-mailmap.)
>
> A helper to read from a set of format-patch output files or a range
> of commits and find those who may have insights to the code that
> the changes touch by running a series of "git blame" commands.
>
> Still needs to add mailmap support and other niceties but the
Trivial correction: mailmap support has been added, so "Still could
use some niceties..."
> basics already look sound, and the enhancements can be done
> in-tree. Assuming that "git contact" is something we may want to
> have as a member of the official set of commands someday, that is.
>
> Will merge to 'next'.
next prev parent reply other threads:[~2013-07-22 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 6:57 What's cooking in git.git (Jul 2013, #07; Sun, 21) Junio C Hamano
2013-07-22 7:15 ` Eric Sunshine [this message]
2013-07-22 7:32 ` Jens Lehmann
2013-07-22 7:48 ` Duy Nguyen
2013-07-22 20:47 ` Jens Lehmann
2013-07-28 17:23 ` Jens Lehmann
2013-07-22 10:39 ` Thomas Rast
2013-07-22 21:39 ` Yamada Saburo
2013-07-22 22:12 ` Junio C Hamano
2013-07-22 22:22 ` John Keeping
2013-07-22 23:13 ` Torsten Bögershausen
2013-07-24 19:03 ` Ramsay Jones
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPig+cQFpddEgkBWYb7fUtijPHCPhtjDu_=wd4br3+qXqLemjg@mail.gmail.com' \
--to=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).