mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jakub Kicinski <kuba@kernel.org>,
	"Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
Cc: jgross@suse.com, x86@kernel.org, pv-drivers@vmware.com,
	Zack Rusin <zackr@vmware.com>, Nadav Amit <namit@vmware.com>,
	Vivek Thampi <vithampi@vmware.com>,
	Vishal Bhakta <vbhakta@vmware.com>,
	Ronak Doshi <doshir@vmware.com>,
	linux-graphics-maintainer@vmware.com,
	dri-devel@lists.freedesktop.org, linux-rdma@vger.kernel.org,
	linux-scsi@vger.kernel.org, netdev@vger.kernel.org,
	linux-input@vger.kernel.org, amakhalov@vmware.com,
	sdeep@vmware.com, virtualization@lists.linux-foundation.org,
	keerthanak@vmware.com, srivatsab@vmware.com, anishs@vmware.com,
	linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [PATCH v3 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases
Date: Wed, 10 Nov 2021 21:19:53 -0800	[thread overview]
Message-ID: <d7f3fec79287a149d6edc828583a771c84646b42.camel@perches.com> (raw)
In-Reply-To: <20211110173935.45a9f495@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

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.


  reply	other threads:[~2021-11-11  5:20 UTC|newest]

Thread overview: 21+ 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
2021-11-11  1:39   ` Jakub Kicinski
2021-11-11  5:19     ` Joe Perches [this message]
     [not found]       ` <20211111055554.4f257fd2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
2021-11-12 17:50         ` Srivatsa S. Bhat
     [not found]         ` <20211112174458.GB11364@csail.mit.edu>
2021-11-12 17:52           ` Joe Perches
2021-11-11 13:46   ` Juergen Gross

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=d7f3fec79287a149d6edc828583a771c84646b42.camel@perches.com \
    --to=joe@perches.com \
    --cc=amakhalov@vmware.com \
    --cc=anishs@vmware.com \
    --cc=doshir@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jgross@suse.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=sdeep@vmware.com \
    --cc=srivatsa@csail.mit.edu \
    --cc=srivatsab@vmware.com \
    --cc=vbhakta@vmware.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=vithampi@vmware.com \
    --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

Powered by JetHome