Hi, I was thinking about that last week. It could indeed be very interesting to have mailmap applied to git-log and especially to git-log --author/--committer. My first look at the code let me think that we would need to change the parse_commit_buffer to replace, at reading time, the name of author and committer if an option (--use-mailmap seems like a wise choice) and probably a config option. The choice of parse_commit_buffer to do the modification is due to the grepping being done directly on buffer when grepping author/committerer. Yet I'm afraid it could be: 1. expensive to rewrite all commit log (reallocating the buffer) 2. Inappropriate to change the value in function that is supposed to read My 2 cents. Cheers, On Mon, Dec 10, 2012 at 7:48 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Rich Midwinter <rich.midwinter@xxxxxxxxx> writes: > >> I'm working on a project for a large organisation that wants to make >> widespread use of git and the mailmap feature. >> >> This seems to be supported by default in git-shortlog but not git-log >> (and other variants) without specifying custom formats, which isn't >> really something I want to try and 'fix' across the organisation. Is >> there a reason for this feature omission or has it just evolved that >> way and could it be fixed? > > I think it was pretty much the latter, but people may already be > depending on the command to give them the "true as recorded back > then" names in the output. A fix may have to involve inventing a > new option "log --use-mailmap" that is explicitly given from the > command line. > > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html