git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: A Large Angry SCM <gitzilla@gmail.com>
Cc: 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 04:52:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0904030447480.10279@pacific.mpi-cbg.de> (raw)
In-Reply-To: <49D54799.9010607@gmail.com>

Hi,

On Thu, 2 Apr 2009, A Large Angry SCM wrote:

> Johannes Schindelin wrote:
> 
> > On Thu, 2 Apr 2009, A Large Angry SCM wrote:
> > 
> > > Junio C Hamano wrote:
> > > > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> > > >
> > > > > > What part of the email address is this going to lowercase? 
> > > > > > Only the domain name is case agnostic.
> > > >
> > > > That is my understanding of RFC, too.  Let's see where this mail 
> > > > goes to find out how much more lenient the real world is ;-).
> > > >
> > > Many email providers/servers are lenient when it comes to case in 
> > > the local part of an email address (after all, they control the 
> > > interpretation) but not every provider/server is and the RFC is VERY 
> > > clear on this issue.
> > 
> > And in one of my projects it is _very_ clear that this strict 
> > interpretation of the RFC, which does not matter in reality, 
> > _actively_ _hurts_.
> 
> Care to provide actual justification for that statement.

Well, I _did_!  I have at least _one_ repository where the case 
insensitive email addresses worked, and got fscked over, by having Git 
change behavior behind my back!

> > In the alternative, can I ask you to adjust my .mailmap in your free 
> > time?
> 
> _Your_ .mailmap file is your issue.
> 
> So which standards do you choose to follow and which do you choose to 
> ignore?

You chose a rather inappropriate moment to start one of those damned 
flamewars -- I am in the middle of some rather important day-job meeting, 
plus two projects in the deadline-is-looming GSoC frenzy.

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.

If you take this mail to start a flamewar for real (i.e. not answer to my 
concerns, but point out that standard X says bla, and that everybody else 
should just obey, oh, and fix their ways as of 20 years), please do remove 
me from the Cc: list.

Ciao,
Dscho

  reply	other threads:[~2009-04-03  2:52 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 [this message]
2009-04-03 12:45                 ` Jeff King
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=alpine.DEB.1.00.0904030447480.10279@pacific.mpi-cbg.de \
    --to=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).