mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nadav Amit <namit@vmware.com>
To: Joe Perches <joe@perches.com>
Cc: "srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
	Juergen Gross <jgross@suse.com>, X86 ML <x86@kernel.org>,
	Pv-drivers <Pv-drivers@vmware.com>,
	Vivek Thampi <vithampi@vmware.com>,
	Vishal Bhakta <vbhakta@vmware.com>,
	Ronak Doshi <doshir@vmware.com>,
	Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Zack Rusin <zackr@vmware.com>, Deep Shah <sdeep@vmware.com>,
	Alexey Makhalov <amakhalov@vmware.com>,
	Linux Virtualization <virtualization@lists.linux-foundation.org>,
	Keerthana Kalyanasundaram <keerthanak@vmware.com>,
	Srivatsa Bhat <srivatsab@vmware.com>,
	Anish Swaminathan <anishs@vmware.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private
Date: Tue, 9 Nov 2021 00:58:48 +0000	[thread overview]
Message-ID: <5C24FB2A-D2C0-4D95-A0C0-B48C4B8D5AF4@vmware.com> (raw)
In-Reply-To: <dcbd19fcd1625146f4db267f84abd7412513d20e.camel@perches.com>



> On Nov 8, 2021, at 4:37 PM, Joe Perches <joe@perches.com> wrote:
> 
> On Mon, 2021-11-08 at 16:22 -0800, Srivatsa S. Bhat wrote:
> 
> So it's an exploder not an actual maintainer and it likely isn't
> publically archived with any normal list mechanism.
> 
> So IMO "private" isn't appropriate.  Neither is "L:"
> Perhaps just mark it as what it is as an "exploder".
> 
> Or maybe these blocks should be similar to:
> 
> M:	Name of Lead Developer <somebody@vmware.com>
> M:	VMware <foo> maintainers <linux-<foo>-maintainers@vmlinux.com>
> 
> Maybe something like a comment mechanism should be added to the
> MAINTAINERS file.
> 
> Maybe #
> 
> so this entry could be something like:
> 
> M:	VMware <foo> maintainers <linux-<foo>-maintainers@vmlinux.com> # VMware's ever changing internal maintainers list

Admittedly, I do not care much about how it turns to be.

But if it is modified, it should be very clear who the maintainer
is, and not to entangle the mailing list and the maintainer.

I am personally not subscribed to the internal pv-drivers mailing
list, which is not just for memory ballooning, and is also listed
as a maintainer for vmmouse, pvscsi, vmxnet3 and others.

As I am the only maintainer of VMware balloon, if someone is
mistaken and sends an email only to the mailing list and not me,
he might be disappointed.


  reply	other threads:[~2021-11-09  0:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 20:29 [PATCH 1/2] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface Srivatsa S. Bhat
2021-11-08 20:30 ` [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private Srivatsa S. Bhat
2021-11-08 20:45   ` Nadav Amit
2021-11-08 23:37   ` Joe Perches
2021-11-09  0:16     ` Jakub Kicinski
2021-11-09  0:22       ` Joe Perches
2021-11-09  0:22     ` Srivatsa S. Bhat
2021-11-09  0:37       ` Joe Perches
2021-11-09  0:58         ` Nadav Amit [this message]
2021-11-09 21:57           ` Joe Perches
2021-11-10 17:20             ` Srivatsa S. Bhat
2021-11-10 17:40               ` Nadav Amit
2021-11-10 19:13                 ` Srivatsa S. Bhat
2021-11-09  5:34   ` Juergen Gross
2021-11-09  5:25 ` [PATCH 1/2] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface 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=5C24FB2A-D2C0-4D95-A0C0-B48C4B8D5AF4@vmware.com \
    --to=namit@vmware.com \
    --cc=Linux-graphics-maintainer@vmware.com \
    --cc=Pv-drivers@vmware.com \
    --cc=amakhalov@vmware.com \
    --cc=anishs@vmware.com \
    --cc=doshir@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgross@suse.com \
    --cc=joe@perches.com \
    --cc=keerthanak@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=netdev@vger.kernel.org \
    --cc=sdeep@vmware.com \
    --cc=srivatsa@csail.mit.edu \
    --cc=srivatsab@vmware.com \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®