git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: CB Bailey <cb@hashpling.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Phil Hord <phil.hord@gmail.com>, Git <git@vger.kernel.org>
Subject: Re: Deadname rewriting
Date: Fri, 21 Jun 2019 23:16:50 +0100	[thread overview]
Message-ID: <20190621221650.hoet5juwjhjcw5mh@hashpling.org> (raw)
In-Reply-To: <877e9e8vxt.fsf@evledraar.gmail.com>

On Fri, Jun 21, 2019 at 11:34:06PM +0200, Ævar Arnfjörð Bjarmason wrote:
> >> This topic was discussed at the last git contributor summit (brought up
> >> by CB Bailey) resulting in this patch, which I see didn't make it in &
> >> needs to be resurrected again:
> >> https://public-inbox.org/git/20181212171052.13415-1-cb@hashpling.org/
> >
> > Thanks for the link.
> >
> > I didn't know about config options for mailmap.file and log.mailmap
> > before. These do make this option much more useful, especially when we
> > can insert default settings for them into /etc/gitconfig across the
> > company.
> 
> Right, and to the extent that we don't --use-mailmap by default I think
> that's mainly because nobody's cared enough to advocate for it. I think
> it would be a sensible default.

That was this patch:

https://public-inbox.org/git/20181213120940.26477-1-cb@hashpling.org/

There were no objections so I was going to re-propose it but I haven't
got around to this for a number of reasons, many of which are not Git
related. Ideally, I wanted to fix all of the known issues with mailmap
such as some behaviors of shortlog fixed with the shortlog patch above.

I also noticed some more artifacts that I would like to be fixed. In
particular the RFC 822 style "trailers" should be rewritten by default.

Having something like this pop up is not likely to be acceptable in a
project which uses trailers:

commit abcd...
Author: Bob <bob@...>

    important commit message

    Signed-off-by: Alice <alice@...?

Obviously it's virtually impossible to account for everything such as
someone referencing Bob by their deadname in the free text body of a
historical commit.

CB

      reply	other threads:[~2019-06-21 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15  1:54 Deadname rewriting Phil Hord
2019-06-15  7:27 ` Andreas Schwab
2019-06-15  8:19 ` Ævar Arnfjörð Bjarmason
2019-06-17 21:21   ` Philip Oakley
2019-06-17 22:33     ` Ævar Arnfjörð Bjarmason
2019-06-21 21:12   ` Phil Hord
2019-06-21 21:34     ` Ævar Arnfjörð Bjarmason
2019-06-21 22:16       ` CB Bailey [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

  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=20190621221650.hoet5juwjhjcw5mh@hashpling.org \
    --to=cb@hashpling.org \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=phil.hord@gmail.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).