From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.81]) by mx.groups.io with SMTP id smtpd.web10.4072.1578059790491364942 for ; Fri, 03 Jan 2020 05:56:30 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aPv73Hde; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: philmd@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578059789; 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=+xDhQskfzJ5h8eIVXCsZn/hZmFmmYkjTxzvwPExBtHA=; b=aPv73Hde0u+Cwk53xvOj4zsynvWjF+PmH7Iys5oHTI2SnFXbQ+hhOudrYcZn8NDfuYb/0w B/I34Rn6kJjcZ6TTe0+h9lqbEsB4ZN/MOFCmQ6WwIPp2+8gXDgc3TZIDXqw8Blv+IQ++pM mbpZxuF78HV2VFv3v3Vs5xD023uGW/Y= 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-57-JVIKkTvZMF6vQ-IYymKGwQ-1; Fri, 03 Jan 2020 08:56:28 -0500 Received: by mail-wm1-f72.google.com with SMTP id f25so1446918wmb.1 for ; Fri, 03 Jan 2020 05:56:27 -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=+xDhQskfzJ5h8eIVXCsZn/hZmFmmYkjTxzvwPExBtHA=; b=NTdxXJAdHWgZPFP+5MZGRNf3Pmi5Yn4bUeVPGwU6fdhE+weipkgGamfnxdxksWjBqJ xjbbWS+TX/M8+RLP+K7ksfeJsJ7e4bdjRiEHNH3XHDAeD6CzHd5y+AkCikokdxqJ5vro pZyAnFN6SUw/EnlV/Wq+CUvHXa6CkG9kkUoAklYGjgNNMew176G8yp9KDKE27QDIZeKv GuRXubj/l1egBCk8ozhZui77IkEMZD/txvKDjv7JDNd3gpgqtp75b6phrkqM6JJ5gN2K vpPmCeindwUrd70H9ilLMJeHOROyTcLPZ+3SyyImOOrZ0ia65dTBpH1ATW+SbfeEfJTg xrpw== X-Gm-Message-State: APjAAAU3pVaOcCWbh8tFcGWETE8Vk/Xi/6h2GF4x0yM6+TPF6FvhP29n KXjBC5uU4s9fXL4gc5ald+P6f+SGzBE7J54MFiL9Q3QO2y5YQ3+gEu1X1O08llT3YBqRa4V7Nig HXKHtfpmQ/m9TNg== X-Received: by 2002:a7b:c5cd:: with SMTP id n13mr19618718wmk.172.1578059787021; Fri, 03 Jan 2020 05:56:27 -0800 (PST) X-Google-Smtp-Source: APXvYqy7CAAeReD69sBe8KMrKMk00PX58rL1h8qVS9ZdPHqQAles2UcALV03HUekIcyriUxCyjvl4A== X-Received: by 2002:a7b:c5cd:: with SMTP id n13mr19618694wmk.172.1578059786792; Fri, 03 Jan 2020 05:56:26 -0800 (PST) Return-Path: Received: from [192.168.1.35] (34.red-83-42-66.dynamicip.rima-tde.net. [83.42.66.34]) by smtp.gmail.com with ESMTPSA id x14sm12123527wmj.42.2020.01.03.05.56.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Jan 2020 05:56:26 -0800 (PST) Subject: Re: [PATCH v3 00/32] .mailmap: Add mailmap file to have a cleaner git history To: Laszlo Ersek , devel@edk2.groups.io Cc: Leif Lindholm , Michael D Kinney , Andrew Fish References: <20200102192345.14600-1-philmd@redhat.com> <07a65a33-8b5c-6479-90f6-c0ef8cd15c9a@redhat.com> From: =?UTF-8?B?UGhpbGlwcGUgTWF0aGlldS1EYXVkw6k=?= Message-ID: <69a63257-d4b7-a715-2db2-457376dd45de@redhat.com> Date: Fri, 3 Jan 2020 14:56:25 +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: <07a65a33-8b5c-6479-90f6-c0ef8cd15c9a@redhat.com> X-MC-Unique: JVIKkTvZMF6vQ-IYymKGwQ-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Laszlo, On 1/3/20 2:48 PM, Laszlo Ersek wrote: > On 01/02/20 20:23, Philippe Mathieu-Daude wrote: >> 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 documentation [1] and [2], and interesting blog [3]. >> >> Laszlo replied [4] to v1 explaining stewards want to avoid avoid >> cross-domain mapping, and suggested to split in per email-address >> patches, so contributors can individually Ack/Nack. >> >> This v3 collects the patches of the 30 developers who replied to >> the v2 [5] with their R-b tag. > > OK. So am I correct to think that this sub-series is ready for merging? > >> There is an exception with patch > > Hmmm... unfinished thought. :) Apparently, there is a patch that > prevents the series from being merged? Which one? This comment was about patch 13/32, but Jiewen Yao already reviewed it, so this series is fully reviewed by each developer. >> I dropped the unreviewed patches and am cc'ing this series to the >> Tianocore stewards, as suggested by Laszlo in [6]. Each developer >> will still be Cc'ed in case a modification was requested, he/her >> can verify. > > Ah, OK, so this is *not* the final version (for round 1, per [6]), just yet. > > Can you please monitor the remaining feedback for this series? If > everyone is happy with the v3 updates, and you determine that the patch > set is fully reviewed, I can help pick up the new tags, and merge the > series. Since the change is a one-line, I'd prefer avoid respining the whole series. IMHO the series is ready for step #4 "stewards go through the backlog, and decide one by one whether, for person X, the proposed mappings are cross-domain or not, and ACK or NACK" which I don't really get. I suppose this will be resolved in the open on the mailing list, so individuals will get notified their patch got refused. Thank for offering to pick and merge this series! Phil. >> >> This series is available at: >> https://gitlab.com/philmd/edk2/commits/mailmap-v3 >> >> Regards, >> >> Phil. >> >> [1] https://git-scm.com/docs/git-shortlog#_mapping_authors >> [2] https://git-scm.com/docs/git-check-mailmap#_mapping_authors >> [3] https://github.com/sympy/sympy/wiki/Using-.mailmap#making-mailmap-entries >> [4] https://edk2.groups.io/g/devel/message/51657 >> [5] https://edk2.groups.io/g/devel/message/51834 >> [6] https://edk2.groups.io/g/devel/message/51906 [...]