git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: A Large Angry SCM <gitzilla@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] mailmap: resurrect lower-casing of email addresses
Date: Fri, 3 Apr 2009 08:45:13 -0400	[thread overview]
Message-ID: <20090403124512.GB21153@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0904030447480.10279@pacific.mpi-cbg.de>

On Fri, Apr 03, 2009 at 04:52:46AM +0200, Johannes Schindelin wrote:

> In case it was not clear yet: if I have to chose between following a 
> standard and reality that just took over, I will _always_ choose the 
> latter.

The problem with "reality" here is that it is not 100% case-insensitive
(and I'm not sure we have anything resembling actual data), and worse,
that the person using git and the person whose reality is case-sensitive
are _different_ people. So you could be breaking email addresses and
have no idea, because the case-sensitivity is implemented on some random
contributor's mail server.

That being said, this is actually restoring behavior broken only about 6
weeks ago (and looks like it was broken in 1.6.2, but no other release).
So I am inclined to say this patch should be applied regardless of
standards and reality if only because it is making git's behavior
consistent across versions. And it looks like Junio has already applied
it.

Now what git _should_ do is another question. Mailmap has been
lower-casing addresses since 5496523 (shortlog: handle email addresses
case-insensitively, 2006-11-19), and I don't think we've had a single
complaint or bug report. Which implies that either reality _is_
primarily case-sensitive, or that people are not actually feeding
mailmap'd addresses to mail servers. So if there is an issue, it is
certainly not pressing, and while I can see and support a concerned
somebody making a patch to address it, I am not that somebody.

Such a patch would have to take into account the very real use case
Dscho is handling, but also address some other real use case (like
cutting and pasting from shortlog output into a MUA).  I assume the
lower-casing is primarily used for aggregating similar addresses; we can
do better to _preserve_ case while matching insensitively (and if there
are multiple cases, then we pick one arbitrarily -- presumably that
address _is_ case insensitive if it was used both ways).

Doing my best to turn a flame war into an actual discussion of merit,

-Peff

  reply	other threads:[~2009-04-03 12:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1238458535u.git.johannes.schindelin@gmx.de>
2009-03-31  0:18 ` [PATCH] mailmap: resurrect lower-casing of email addresses Johannes Schindelin
2009-04-02 22:22   ` A Large Angry SCM
2009-04-02 22:39     ` Johannes Schindelin
2009-04-02 22:42       ` Junio C Hamano
2009-04-02 22:58         ` A Large Angry SCM
2009-04-02 23:08           ` Johannes Schindelin
2009-04-02 23:17             ` A Large Angry SCM
2009-04-03  2:52               ` Johannes Schindelin
2009-04-03 12:45                 ` Jeff King [this message]
2009-04-04  1:32                 ` A Large Angry SCM
2009-04-06  9:16                   ` Johannes Schindelin
2009-04-07  2:08                     ` A Large Angry SCM
2009-04-07 11:16                       ` Johannes Schindelin
2009-04-07 19:58                         ` Markus Heidelberg
2009-04-08  9:36                           ` Alles wird Git, was " Johannes Schindelin
2009-04-08  0:50                         ` A Large Angry SCM
2009-04-08  2:21                           ` Alles wird Git, was " Johannes Schindelin
2009-04-08 11:20                             ` Alles wird Git A Large Angry SCM
2009-04-04  1:51                 ` [PATCH] mailmap: resurrect lower-casing of email addresses A Large Angry SCM
2009-04-07  5:52   ` Marius Storm-Olsen

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=20090403124512.GB21153@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gitzilla@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).