From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.120]) by mx.groups.io with SMTP id smtpd.web10.4141.1575641523925165571 for ; Fri, 06 Dec 2019 06:12:04 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=NqmsumNW; spf=pass (domain: redhat.com, ip: 207.211.31.120, mailfrom: philmd@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1575641523; 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=StOeAc0Wl36I8LTc1h515KCE+UKncew6iW4dC8VR5yg=; b=NqmsumNW1d6aeFnkGvmx1UZq2OkcW9Rh9vvwdy0YD+nneZNhActzVIYdeeZhkUKosznZz9 xiD/O/tZnu2RRMID6GsecicC2a5UgrEuURGLkZBStaO6FAukM0DKUSmSqbnySYOhVMmZGa uVAeBoicmTuVZacc2PaTjOOT8fKe5ec= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-195-aa6WiYMbOH2IFf-w40m4Bg-1; Fri, 06 Dec 2019 09:12:01 -0500 Received: by mail-wm1-f69.google.com with SMTP id l11so5464236wmi.0 for ; Fri, 06 Dec 2019 06:12:01 -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=StOeAc0Wl36I8LTc1h515KCE+UKncew6iW4dC8VR5yg=; b=WRGTriabIMjBeLf4QAE5zJEjrBnIb2qOdZTRHbyzrEX8/ooMxwmJRZrowUqia+EMDW 8pb4L6FIBvCAFBVfnI8IeIg6KKNK470NB/h7LsNCZNykoZ4WPcteVe6lVZIxUspzLAu+ prkQkEw9OPFfStr48rO7DPHI4Kl6azXLZV1BZfwvuZjPMNV4FEcm2USmJTDX1KxQEGRE 1xqkXBU8RV0PPF8XOG7qmXbXbzgW/afYPs4k/mskLvcFnv/Mi7OC546ZiiLs0DODzssN EPU6dfJ4mTQPPGH63DEEP/1cjuKFH1aI2PfYcYqPT9Yks9RuimJEoRCFdVgF/BnWFuzS Y0zQ== X-Gm-Message-State: APjAAAVfdOFDv1QSw5XZzZFPALeq5lPmhR1aeP+uKpUzxn1QNeA3ViOq +BCaY5VYsvpxIeIT2HQUhud/JtESC+/8sFRvpLUnzy66beNQapMXf0sdp0YfemClOJDy1108ixD iIg1JDk56ejrUjQ== X-Received: by 2002:a1c:8086:: with SMTP id b128mr10878775wmd.80.1575641520282; Fri, 06 Dec 2019 06:12:00 -0800 (PST) X-Google-Smtp-Source: APXvYqzod7km7HdvY2E/8R3ALjIcmj3H0U1GygXFUv1tEkzrSvD2IusqLn46Cw2DdHk8s8G4S5ZpYQ== X-Received: by 2002:a1c:8086:: with SMTP id b128mr10878760wmd.80.1575641520089; Fri, 06 Dec 2019 06:12:00 -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 d14sm17075636wru.9.2019.12.06.06.11.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 06 Dec 2019 06:11:59 -0800 (PST) Subject: Re: [PATCH v2 000/105] .mailmap: Add mailmap file to have a cleaner git history To: Laszlo Ersek , devel@edk2.groups.io Cc: Andrew Fish , Leif Lindholm , Michael D Kinney References: <20191206112638.23175-1-philmd@redhat.com> <9e212952-a114-57d0-9880-6686edc4d8ae@redhat.com> From: =?UTF-8?B?UGhpbGlwcGUgTWF0aGlldS1EYXVkw6k=?= Message-ID: <1e4d7154-e678-9ddb-82e0-4264735ba8f6@redhat.com> Date: Fri, 6 Dec 2019 15:11:58 +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: <9e212952-a114-57d0-9880-6686edc4d8ae@redhat.com> X-MC-Unique: aa6WiYMbOH2IFf-w40m4Bg-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 12/6/19 1:23 PM, Laszlo Ersek wrote: > On 12/06/19 12:24, 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. >> Similarly, stewards can Nack if there is a cross-domain issue, since >> these are not obvious to me (they would happen if someone was working >> for a company at the time the repository was using SVN, the switched >> company and contributed later at the time the repository was passed >> to GIT). > > I suggest the following: > > - Collect feedback (from individual reviewers / contributors) for one or > two weeks > > - Accept cross-domain mappings in any patch where the person subject to > the patch is ACKing the patch from the mapped-to (i.e. "current") email > address. This is now a *lot* easier to do, because the patch series is > structured by person. > > - After one or two weeks, push all the patches that have been approved > like explained above. > > - Repost the rest of the series, CC'd solely to the stewards. We will > then have to 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 > accordingly. > > - Push the second round, drop the rest for good. This works for me, thanks! > > So in this first review iteration, we really depend on people to respond > from their "new" (mapped-to) addresses. > > Fantastic job on the split-per-person! > > Thanks! > Laszlo