From: Junio C Hamano <gitster@pobox.com>
To: Marius Storm-Olsen <marius@trolltech.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4 1/4] Add log.mailmap as configurational option for mailmap location
Date: Thu, 05 Feb 2009 12:22:22 -0800 [thread overview]
Message-ID: <7v63jod475.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <498B3F24.6080305@trolltech.com> (Marius Storm-Olsen's message of "Thu, 05 Feb 2009 20:33:56 +0100")
Marius Storm-Olsen <marius@trolltech.com> writes:
> Given that in total shortlog, blame, log, diff-tree, rev-list, show
> and whatchanged use it (the latter 5 through the pretty option), I'm
> tempted to say that it justifies its own option (mailmap.file?); but
> it would still have to be handled by git_default_config(). Renaming it
> would give it stronger reason to *be there* though.
We are in total agreement then ;-)
I also agree that it would be a good idea to introduce a shared
documentlet similar to pretty-format.txt that can be included in the
documentation pages of commands that use this name-rewriting mechanism.
prev parent reply other threads:[~2009-02-05 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 8:06 [PATCH v4 0/4] Extend mailmap functionality Marius Storm-Olsen
2009-02-05 8:06 ` [PATCH v4 1/4] Add log.mailmap as configurational option for mailmap location Marius Storm-Olsen
2009-02-05 8:06 ` [PATCH v4 2/4] Add find_insert_index, insert_at_index and clear_func functions to string_list Marius Storm-Olsen
2009-02-05 8:06 ` [PATCH v4 3/4] Add map_user() and clear_mailmap() to mailmap Marius Storm-Olsen
2009-02-05 8:06 ` [PATCH v4 4/4] Change current mailmap usage to do matching on both name and email of author/committer Marius Storm-Olsen
2009-02-05 17:44 ` [PATCH v4 1/4] Add log.mailmap as configurational option for mailmap location Junio C Hamano
2009-02-05 19:33 ` Marius Storm-Olsen
2009-02-05 20:22 ` Junio C Hamano [this message]
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=7v63jod475.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=marius@trolltech.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).