From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: Jakub Kicinski <kuba@kernel.org>, Joe Perches <joe@perches.com>
Cc: Ronak Doshi <doshir@vmware.com>,
pv-drivers@vmware.com, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
Nadav Amit <namit@vmware.com>,
amakhalov@vmware.com, linux-scsi@vger.kernel.org,
Vishal Bhakta <vbhakta@vmware.com>,
x86@kernel.org, linux-graphics-maintainer@vmware.com,
linux-input@vger.kernel.org, rostedt@goodmis.org,
keerthanak@vmware.com, jgross@suse.com, anishs@vmware.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, Zack Rusin <zackr@vmware.com>
Subject: Re: [PATCH v3 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases
Date: Fri, 12 Nov 2021 09:50:33 -0800 [thread overview]
Message-ID: <fd9df647-4c1a-b4fb-159b-4876bc5cd0b6@csail.mit.edu> (raw)
In-Reply-To: <20211111055554.4f257fd2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
[ Resending since my previous reply didn't reach the mailing lists. ]
On 11/11/21 5:55 AM, Jakub Kicinski wrote:
> On Wed, 10 Nov 2021 21:19:53 -0800 Joe Perches wrote:
>> On Wed, 2021-11-10 at 17:39 -0800, Jakub Kicinski wrote:
>>> On Wed, 10 Nov 2021 12:09:06 -0800 Srivatsa S. Bhat wrote:
>>>> DRM DRIVER FOR VMWARE VIRTUAL GPU
>>>> -M: "VMware Graphics" <linux-graphics-maintainer@vmware.com>
>>>> M: Zack Rusin <zackr@vmware.com>
>>>> +R: VMware Graphics Reviewers <linux-graphics-maintainer@vmware.com>
>>>> L: dri-devel@lists.freedesktop.org
>>>> S: Supported
>>>> T: git git://anongit.freedesktop.org/drm/drm-misc
>>>
>>> It'd be preferable for these corporate entries to be marked or
>>> otherwise distinguishable so that we can ignore them when we try
>>> to purge MAINTAINERS from developers who stopped participating.
>>>
>>> These addresses will never show up in a commit tag which is normally
>>> sign of inactivity.
>>
>> Funny.
>>
>> The link below is from over 5 years ago.
>>
>> https://lore.kernel.org/lkml/1472081625.3746.217.camel@perches.com/
>>
>> Almost all of those entries are still in MAINTAINERS.
>>
>> I think the concept of purging is a non-issue.
>
> I cleaned networking in January and intend to do it again in 2 months.
> See:
>
> 054c4610bd05 MAINTAINERS: dccp: move Gerrit Renker to CREDITS
> 4f3786e01194 MAINTAINERS: ipvs: move Wensong Zhang to CREDITS
> 0e4ed0b62b5a MAINTAINERS: tls: move Aviad to CREDITS
> c41efbf2ad56 MAINTAINERS: ena: remove Zorik Machulsky from reviewers
> 5e62d124f75a MAINTAINERS: vrf: move Shrijeet to CREDITS
> 09cd3f4683a9 MAINTAINERS: net: move Alexey Kuznetsov to CREDITS
> 93089de91e85 MAINTAINERS: altx: move Jay Cliburn to CREDITS
> 8b0f64b113d6 MAINTAINERS: remove names from mailing list maintainers
>
I'm assuming the purging is not totally automated, is it? As long as
the entries are informative to a human reader, it should be possible
to skip the relevant ones when purging inactive entries.
I believe this patch makes the situation better than it is currently
(at least for the human reader), by marking lists without public
read-access in a format that is more appropriate. In the future, we
could perhaps improve on it to ease automation too, but for now I
think it is worthwhile to merge this change (unless there are strong
objections or better alternatives that everyone agrees on).
Regards,
Srivatsa
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-11-12 17:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 20:07 [PATCH v3 0/3] Update VMware maintainer entries Srivatsa S. Bhat
2021-11-10 20:08 ` [PATCH v3 1/3] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface Srivatsa S. Bhat
2021-11-11 6:50 ` Greg KH
2021-11-11 13:57 ` Steven Rostedt
2021-11-11 15:39 ` Srivatsa S. Bhat
2021-11-11 18:45 ` Greg KH
2021-11-11 19:40 ` Srivatsa S. Bhat
2021-11-12 6:55 ` Greg KH
2021-11-12 17:31 ` Srivatsa S. Bhat
2021-11-12 17:16 ` Sasha Levin
2021-11-15 22:39 ` Srivatsa S. Bhat
2021-11-16 4:33 ` Joe Perches
2021-11-16 18:18 ` Srivatsa S. Bhat
2021-11-16 23:11 ` Joe Perches
2021-11-10 20:08 ` [PATCH v3 2/3] MAINTAINERS: Add Zack as maintainer of vmmouse driver Srivatsa S. Bhat
2021-11-10 20:09 ` [PATCH v3 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases Srivatsa S. Bhat
[not found] ` <20211110173935.45a9f495@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
2021-11-11 5:19 ` Joe Perches
[not found] ` <20211111055554.4f257fd2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
2021-11-12 17:50 ` Srivatsa S. Bhat [this message]
2021-11-11 13:46 ` Juergen Gross via Virtualization
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd9df647-4c1a-b4fb-159b-4876bc5cd0b6@csail.mit.edu \
--to=srivatsa@csail.mit.edu \
--cc=amakhalov@vmware.com \
--cc=anishs@vmware.com \
--cc=doshir@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgross@suse.com \
--cc=joe@perches.com \
--cc=keerthanak@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=namit@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=rostedt@goodmis.org \
--cc=vbhakta@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=zackr@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).