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 vsement...@virtuozzo.com is not accessible anymore. > > > > > > > > > > Signed-off-by: Vladimir Sementsov-Ogievskiy <v.sementsov...@mail.ru> > > > > > --- > > > > > > > > > > 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
