From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mx.groups.io with SMTP id smtpd.web12.6453.1600775760780453690 for ; Tue, 22 Sep 2020 04:56:00 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZVQ4qFTj; spf=pass (domain: redhat.com, ip: 63.128.21.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1600775760; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JjMnPaONMeNZlqAhGMaUntHMB4MEyArzKcSCVynfnkw=; b=ZVQ4qFTjAATm5jQNVvPGd7RSu8R7lFcCW9w12H9vdlAbRbaAm3DQU+X4pRVu4LljmigLt3 Q8hyhQKbhgyeOEp1+EXHCQve/eZF8SNYjbp7fXaRLa7rShhB30X9mSm8CltZaHjZASvf/d t8iMomjvsltIJoGUWOdaf6bewSWDCzo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-584-9lRMktvdNPW22eJjghT-Bg-1; Tue, 22 Sep 2020 07:55:58 -0400 X-MC-Unique: 9lRMktvdNPW22eJjghT-Bg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 4C4E88064BA; Tue, 22 Sep 2020 11:55:57 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-169.ams2.redhat.com [10.36.114.169]) by smtp.corp.redhat.com (Postfix) with ESMTP id 626E67368E; Tue, 22 Sep 2020 11:55:56 +0000 (UTC) Subject: Re: [PATCH 02/22] .mailmap: add entry for Ching JenX Cheng To: =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= , edk2-devel-groups-io Cc: Ching JenX Cheng References: <20200907193102.30535-1-lersek@redhat.com> <20200907193102.30535-3-lersek@redhat.com> <0f2cd251-f120-0fd6-714a-1b083b114c6e@redhat.com> <1f85ff18-98e6-be79-63f0-8f6fbfa4d1ab@redhat.com> <6b88cbd4-39bf-d877-d17a-5294bb130182@redhat.com> From: "Laszlo Ersek" Message-ID: <0181837c-f957-faf5-1089-84e89996b229@redhat.com> Date: Tue, 22 Sep 2020 13:55:55 +0200 MIME-Version: 1.0 In-Reply-To: <6b88cbd4-39bf-d877-d17a-5294bb130182@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US On 09/22/20 11:38, Philippe Mathieu-Daudé wrote: > On 9/22/20 9:22 AM, Laszlo Ersek wrote: >> On 09/17/20 18:45, Philippe Mathieu-Daudé wrote: >> >>> OK I didn't know the format has to follow the English name order. >>> I used the Chinese name order because I found somewhere in the >>> EDK2 archives some posts signed as "Cheng Ching Jen", so I took >>> this order to respect the author preference. >> >> Thanks -- this is a convincing argument. >> >> Gives me the following idea: the mailmap file supports comments (see at >> the end of git-shortlog). Thus, at least when we extend our own mailmap >> for edk2, we should always include some references (mailing list links, >> commit hashes, etc) near the newly added entries that justify the entries. > > Ah this is an excellent idea, Thanks! > that way we could fix old contributions > even if the contributor left the community. To clarify: this was meant for our own mailmap for edk2 (out-of-tree); that is, *not* the .mailmap file in the edk2 project root directory. Again -- my experience with this 22-part patch set tells me that it makes no sense to spend time improving the upstream .mailmap file. Because, feedback has been extremely lacking. So the "use comments" trick would apply to the mailmap file that we would maintain *outside* of edk2, just for our particular purposes (git-dm, git-shortlog for QEMU's edk2 submodule updates, etc). I'll go ahead and merge the patches from this series that have been approved by the respective email addresses' owners, and drop the rest. (We could incorporate them into the out-of-tree mailmap file, later.) Thanks Laszlo