Git development
 help / color / mirror / Atom feed
From: CB Bailey <cb@hashpling.org>
To: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Use mailmap by default in log, show and whatchanged
Date: Thu, 13 Dec 2018 12:12:03 +0000	[thread overview]
Message-ID: <20181213121203.zzzwaadf73cbfrkn@hashpling.org> (raw)
In-Reply-To: <20181213120940.26477-1-cb@hashpling.org>

On Thu, Dec 13, 2018 at 12:09:40PM +0000, CB Bailey wrote:
> I had a dig around in the mailing list archives and couldn't find any
> specific reason not to use a mailmap in log where one is in use. I did
> find this message which suggests that it makes sense to make it the
> default for human-consumed formats. This patch doesn't affect
> "--pretty=raw" formatting.

This week I'm having an issue with sending messages a few seconds before
I've completed them.

This message:
https://public-inbox.org/git/20121112231815.GE10531@sigill.intra.peff.net/

CB

  reply	other threads:[~2018-12-13 12:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 12:09 [RFC/PATCH] Use mailmap by default in log, show and whatchanged CB Bailey
2018-12-13 12:12 ` CB Bailey [this message]
2018-12-13 13:49 ` Johannes Schindelin

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=20181213121203.zzzwaadf73cbfrkn@hashpling.org \
    --to=cb@hashpling.org \
    --cc=git@vger.kernel.org \
    /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