From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.61]) by mx.groups.io with SMTP id smtpd.web09.487.1575400521311923294 for ; Tue, 03 Dec 2019 11:15:21 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=QApidgAh; spf=pass (domain: redhat.com, ip: 205.139.110.61, mailfrom: philmd@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1575400520; 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=8j1n6/HqePPsQ6zbb8H24cSPltl4g+doqeFg/b93oYw=; b=QApidgAh02mGoz/IT7r7zSGPWH4Yyx4sMFwf4fLJi0nB6szPnuHkY1Ad+hRZWKEz9tq+8A RP9lvwTC7xkLlzuExyrARbZs51DMWjJ3lTYKOi7eOnsxSJA3yZbHfgv/gK/hLjcrjqY5kf HogqehI/pDF6d/ux1qv6JfSRMW1czcs= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-356-lrjTaQQgP_u4N6VFuKJ61g-1; Tue, 03 Dec 2019 14:15:13 -0500 Received: by mail-wm1-f72.google.com with SMTP id o135so1346043wme.2 for ; Tue, 03 Dec 2019 11:15:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=GDrMK5yJU1fSqyPVy3KMPTeSpntfFqs7v6wZ215gNNA=; b=BYEJ942uRTcH0Erf6tntmJbUhMeZWxf/y7pG9ZMM2N8wYZfuGL0h0GB+xavmHhB9y0 6UzfgiKeki5XPMXCIcmZa3X4jXGrBmeneRoSeCaQuKCxjINQlkl6XJtrJqZ6VzjVg+6o TZfwkDHF83tZSgW6Bn1p5qA4XRcAuiwxZY2UF1Ds/W+OmlkKuS5mUoe9ZY0ygXo5Chgv PM0QKLJQyXIpsIxpgofFAbDjgxgXUtp6F+LYTR4csQx6OQgTIWXEMDjm7rfV644lFRnZ SXtXox03c7hAnu1nGTx0r6oReF1CI29xPwCEZiyE5EU2GVREApTNF0mQKbo50JPbSHh/ QDAA== X-Gm-Message-State: APjAAAVYCZUNOixBjM8QI6oedXnxHJnjtQ1tYUh0tbFAsAc3zb0sLvdR GSV7hBeegH1s3QdMWQJprtodFo42LP1I8KPv7QaL3BhSyKNEmgDYCV1t5h66FwQS4YMtyLCPZ+B v3ojteapxPlSkgw== X-Received: by 2002:a7b:c10c:: with SMTP id w12mr37421396wmi.114.1575400512299; Tue, 03 Dec 2019 11:15:12 -0800 (PST) X-Google-Smtp-Source: APXvYqw0lCMH8/eWSZ+FpITf/hFckx0zqYcROdOM2A2396wAyj0Pf/xJ7vKUCZl0VgLckZ4DHyY/ig== X-Received: by 2002:a7b:c10c:: with SMTP id w12mr37421377wmi.114.1575400512068; Tue, 03 Dec 2019 11:15:12 -0800 (PST) Return-Path: Received: from [192.168.1.35] (182.red-88-21-103.staticip.rima-tde.net. [88.21.103.182]) by smtp.gmail.com with ESMTPSA id k19sm3928027wmi.42.2019.12.03.11.15.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Dec 2019 11:15:11 -0800 (PST) Subject: Re: [edk2-devel] [PATCH 0/8] .mailmap: Add mailmap file to have a cleaner git history To: Laszlo Ersek Cc: devel@edk2.groups.io, Michael Kinney , Brian Richardson , Andrew Fish , Leif Lindholm References: <20191126150838.5858-1-philmd@redhat.com> From: =?UTF-8?B?UGhpbGlwcGUgTWF0aGlldS1EYXVkw6k=?= Message-ID: Date: Tue, 3 Dec 2019 20:15:09 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: X-MC-Unique: lrjTaQQgP_u4N6VFuKJ61g-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable On 12/3/19 7:51 PM, Laszlo Ersek wrote: > Hi Phil, >=20 > (heavily trimmer CC list) Good idea :) > On 11/26/19 16:08, Philippe Mathieu-Daud=C3=A9 via Groups.Io wrote: >> Hi, >> >> The .mailmap git feature helps fixing commit mistakes (in name/email). >> >> The easiest way to use it is with the --use-mailmap flag: >> >> $ git log --use-mailmap >> >> See: >> https://git-scm.com/docs/git-shortlog#_mapping_authors >> https://git-scm.com/docs/git-check-mailmap#_mapping_authors >> >> Also interesting: >> https://github.com/sympy/sympy/wiki/Using-.mailmap#making-mailmap-entrie= s >> >> Regards, >> >> Phil. >> >> Philippe Mathieu-Daud=C3=A9 (8): >> .mailmap: Convert emails generated by the Subversion original import >> .mailmap: Fix emails from the Subversion era >> .mailmap: Fix Intel emails rewritten by Microsoft Exchange Server >> .mailmap: Fix emails rewritten by lists DMARC / DKIM / SPF >> .mailmap: Fix incorrect email formats >> .mailmap: Unify Intel email addresses format >> .mailmap: Fix UTF-8 mojibaked names >> .mailmap: Miscellaneous fixes on various emails >> >> .mailmap | 221 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> 1 file changed, 221 insertions(+) >> create mode 100644 .mailmap >> >=20 > our suggestion from the stewards' confcall is to avoid cross-domain > mappings, unless a contributor explicitly confirms (in an email sent > from the mapped-to, i.e. "new" address) that they are OK with the > mapped-from (i.e. "old") address being "hidden" by the mapping. >=20 > Due to two reasons: > - mappings across domains could hide employer changes, Hmm OK. > - even the "mapped-to" (i.e. "new") address may not be up-to-date. Agreed. > Stewards may be able ACK typo fixes and simple name order changes even > in the absence of the affected (historical) contributor, but > cross-domain mappings are not something they can ACK on their own. Understood. > (At least this is my understanding from the meeting.) >=20 > Personal note in the end: can we perhaps structure this patch set per > email adress / "liveliness groups"? I think most people will ignore a > patch that has tens of CC's, even if their personal ACK is needed for > it. On the other hand, if we have 60-100 patches, but each patch is just > emailed to 2-3 people (and any given person only gets a very low number > of personal patch emails), such a series has a better chance at > succeeding. (We could even commit such a set piece-meal -- commit the > most recently ACKed subset every week or every two weeks.) Just some > speculation on my part. Yes, I'll try to find a clever way. (I had the v2 ready, but I was waiting to figure out how to restrict to=20 100 recipients).