Messages in this thread | | | Subject | Re: [PATCH v3 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases | From | Joe Perches <> | Date | Fri, 12 Nov 2021 09:52:23 -0800 |
| |
On Fri, 2021-11-12 at 09:44 -0800, Srivatsa S. Bhat wrote: > On Thu, Nov 11, 2021 at 05:55:54AM -0800, 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: [] > > 8b0f64b113d6 MAINTAINERS: remove names from mailing list maintainers
I think the last removal of descriptive naming from exploder style reviewers or mailing lists is misguided/not good.
I suggest this change be reverted.
> 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.
true
> 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).
I think this VMware suggested patch to MAINTAINERS is good and improves readers ability to know how any suggested patch is going to be reviewed by a company..
| |