git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: torvalds@osdl.org, git@vger.kernel.org
Subject: git-shortlog mailmap
Date: Thu, 26 Oct 2006 14:34:24 +0200	[thread overview]
Message-ID: <20061026123424.GQ20017@pasky.or.cz> (raw)
In-Reply-To: <ehputm$ch2$3@sea.gmane.org>

I think I've complained about this in the past, but can't find the mail.

Dear diary, on Thu, Oct 26, 2006 at 11:25:50AM CEST, I got a letter
where Jakub Narebski <jnareb@gmail.com> said that...
> Johannes Schindelin wrote:
> 
> > BTW what happened to the builtin shortlog? It is the last Perl script I 
> > use regularly... (should make people happy who are stuck with Activision 
> > Perl...)
> 
> BTW. both Perl version and builtin shorlog have email->real name translation
> table built in. In Perl script version it is in __DATA__ section, and we
> could update it using Inline::Files module, in C version it was in table.
> But in fact this list is project specific. Shouldn't we make it customizable
> (::sigh::, yet another file in $GIT_DIR...).

I really dislike the fact that we _do_ this mapping at all, this seems
so much a totally wrong point at which to do it. The information tracked
in Git is still wrong and all the tools except shortlog still display it
wrong - why should shortlog in particular be special? Why don't we do
this at the git-am time instead?

And overally, things would be simpler if people would just require the
author name to be recorded in the mail properly when applying the patch;
AIUI at least in case of the kernel this mapping shouldn't really be
needed anymore anyway since with the signoff protocol, you already
require all the contributors to reveal their realnames in signoffs?
People can then as well just write that in their from headers as well.
Linus?

So what about making git-am by default refuse to apply patches with
missing author realnames?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1

  parent reply	other threads:[~2006-10-26 12:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26  8:47 What's in git.git Junio C Hamano
2006-10-26  9:12 ` Jakub Narebski
2006-10-26  9:24   ` Junio C Hamano
2006-10-26 12:08   ` Petr Baudis
2006-10-26 12:17     ` Jakub Narebski
2006-10-26  9:18 ` merge-recursive, was " Johannes Schindelin
2006-10-26  9:25   ` Jakub Narebski
2006-10-26  9:35     ` Junio C Hamano
2006-10-26  9:47       ` Jakub Narebski
2006-10-26 13:23       ` Nicolas Pitre
2006-10-26 12:34     ` Petr Baudis [this message]
2006-10-26 12:41       ` git-shortlog mailmap Jakub Narebski
2006-10-26 12:43         ` Andreas Ericsson
2006-10-26 13:13           ` Jakub Narebski
2006-10-26 13:16             ` Johannes Schindelin
2006-10-26 13:29         ` Petr Baudis
2006-10-26  9:26   ` merge-recursive, was Re: What's in git.git Junio C Hamano
2006-10-26 10:00     ` Junio C Hamano
2006-10-26 10:56       ` Johannes Schindelin
2006-10-26 11:35   ` shortlog, was " Andreas Ericsson
2006-10-26 13:39     ` Nicolas Pitre
2006-10-26 13:45       ` Andreas Ericsson
2006-10-26  9:19 ` Jakub Narebski
2006-10-27  1:10   ` Petr Baudis
2006-10-26 12:22 ` Petr Baudis
2006-10-26 17:27 ` Andy Whitcroft

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=20061026123424.GQ20017@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=torvalds@osdl.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.
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).