From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 432AAC433EF for ; Mon, 21 Mar 2022 20:46:47 +0000 (UTC) Received: from localhost ([::1]:46352 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nWOvN-0003ko-S2 for qemu-devel@archiver.kernel.org; Mon, 21 Mar 2022 16:46:45 -0400 Received: from eggs.gnu.org ([209.51.188.92]:39192) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nWOtE-0002iK-LY for qemu-devel@nongnu.org; Mon, 21 Mar 2022 16:44:32 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:24961) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nWOtC-00006q-9J for qemu-devel@nongnu.org; Mon, 21 Mar 2022 16:44:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1647895469; 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: in-reply-to:in-reply-to:references:references; bh=zYOtubC+7E3DKPhMm+tljMhQH47bVACfa6wmSiSmKSE=; b=hr0XVYfc8KMln4r8lF9SwNnCmYg6f4HGJfBlWhs0AIyCaA2vsHaf/y14fzvv/+OjRzggAs CaUPMd9DAPpLxVUDhsTIsTUQPeFx5LC4z2+YEWjwIcxS67XrcYmklK4zc8xpa6NjMEuEkc ydeO05fg+Z7GnBfpaE4WmE3P6rMO8pA= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-29-p6HpPuw6N129Nk2is56-DA-1; Mon, 21 Mar 2022 16:44:26 -0400 X-MC-Unique: p6HpPuw6N129Nk2is56-DA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 9A8448038E3; Mon, 21 Mar 2022 20:44:25 +0000 (UTC) Received: from redhat.com (unknown [10.2.16.194]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3DEA540C1241; Mon, 21 Mar 2022 20:44:25 +0000 (UTC) Date: Mon, 21 Mar 2022 15:44:23 -0500 From: Eric Blake To: Vladimir Sementsov-Ogievskiy Subject: Re: [PATCH v2] MAINTAINERS: change Vladimir's email address Message-ID: <20220321204423.2ggfljmv7ay33pmw@redhat.com> References: <20220316092702.426629-1-v.sementsov-og@mail.ru> <20220316213620.yrc6fvskjqabogoi@redhat.com> <3e0a174c-71e1-2308-855e-0cc9102a8ee0@mail.ru> <20220321201251.ohhzthftzmijihf2@redhat.com> MIME-Version: 1.0 In-Reply-To: User-Agent: NeoMutt/20211029-454-6adf99 X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=eblake@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Received-SPF: pass client-ip=170.10.129.124; envelope-from=eblake@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -21 X-Spam_score: -2.2 X-Spam_bar: -- X-Spam_report: (-2.2 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.082, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Mon, Mar 21, 2022 at 11:31:18PM +0300, Vladimir Sementsov-Ogievskiy wrote: > 21.03.2022 23:12, Eric Blake wrote: > > On Thu, Mar 17, 2022 at 11:24:28AM +0300, Vladimir Sementsov-Ogievskiy wrote: > > > 17.03.2022 00:36, Eric Blake wrote: > > > > On Wed, Mar 16, 2022 at 12:27:02PM +0300, Vladimir Sementsov-Ogievskiy wrote: > > > > > Old vsementsov@virtuozzo.com is not accessible anymore. > > > > > > > > > > Signed-off-by: Vladimir Sementsov-Ogievskiy > > > > > --- > > > > > > > > > > v2: @ya.ru mailbox works bad with mailing lists and git send-email > > > > > command, @mail.ru works normally. > > > > > > > > > > Probably, I'll have to change the email again in the near future. May be > > > > > not. But I think it worth to change it now to something that works. > > > > > > > > Same comment as with your attempt with @ya.ru - I'm happy to > > > > incorporate this through my NBD tree, but want to confirm that we had > > > > a round-trip conversation so that you are happy with the address > > > > working to your needs. > > > > > > > > > > It works) > > > > Okay, I'm queueing this up through my NBD tree. Do you also want to > > tweak .mailmap and/or contrib/gitdm/aliases? > > > > I looked them through, but didn't finally understand, how they are used, and therefore, is it really needed. They're both optional, so I won't hold up this patch as written. Among other things, .mailmap lets 'git shortlog' and similar combine all commits by two different email addresses but one underlying author under a single group, rather than one group per email address. It is most commonly used to correct spelling errors (for example, altering your spelling to take advantage of UTF-8 characters, or correcting an email sent from a username instead of a Proper Name), but does have a section for # Next, replace old addresses by a more recent one. which can be useful for someone trying to follow up to a patch's original author to reach that author by their now-preferred address. contrib/gitdm/aliases is similar, but more concerned when running status reports of how many commits were contributed from a given company vs. an individual contributor. Here, merging a company and a personal address makes sense if you freely post from both accounts but want all your patches to be tied to your employer, and makes less sense if you want a clear line of delineation between patches you did on your own time instead of for employment. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org