All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Petr Vandrovec <petr@vandrovec.name>
Cc: pv-drivers@vmware.com, linux-graphics-maintainer@vmware.com,
	Petr Vandrovec <petr@vmware.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: MAINTAINERS without commits in the last 3 years
Date: Wed, 24 Aug 2016 17:24:23 -0700	[thread overview]
Message-ID: <1472084663.3746.234.camel@perches.com> (raw)
In-Reply-To: <CA+i2_Ddvg9a0S23ywJtXQbLuq3JLJF9poH=n_G1+9uWWVPZwOg@mail.gmail.com>

On Wed, 2016-08-24 at 17:17 -0700, Petr Vandrovec wrote:
> Hi,

Hi Petr.

> I (petr@vandrovec.name) am "maintainer" of ncpfs.  As NetWare is dead for
> decade or so, there are no new users, and so no new bugs are found, and no
> new features needs to be added. And so no checkins are needed.

No worries, that's great.

> I have no idea how many people would be affected by ncpfs removal, but as
> long as it stays in the kernel, I guess I have most experience with it.

I wasn't proposing remove any code, just updating
any invalid or old maintainer addresses.

> Other address I know something about is pv-drivers@vmware.com.  It is group
> of people responsible for Linux drivers at VMware, so it is right place to
> send patches.  As each of them has their own email address, you will never
> see this in checkin messages.
> 
> Same applies to linux-graphics-maintainer@vmware.com, that is address for
> patches to all VMware graphics drivers, both in kernel & X.
> 
> So it would be great if you can keep these.

I certainly won't submit any patch removing those.

cheers, Joe

> > linux-graphics-maintainer@vmware.com
> > petr@vandrovec.name
> > pv-drivers@vmware.com

  parent reply	other threads:[~2016-08-25  7:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 23:33 MAINTAINERS without commits in the last 3 years Joe Perches
     [not found] ` <CA+i2_Ddvg9a0S23ywJtXQbLuq3JLJF9poH=n_G1+9uWWVPZwOg@mail.gmail.com>
2016-08-25  0:24   ` Joe Perches [this message]
     [not found] ` <CAHrUA37xh-6GLkTAM75w8v550rR8n2Ayycjy9FNofv3K+=QoVQ@mail.gmail.com>
2016-08-25  2:09   ` Joe Perches
2016-08-25  3:26 ` Alexander Graf
2016-08-25  7:01 ` Ali Akcaagac
2016-08-25  7:29 ` Steve Twiss
2016-08-25 10:12 ` Mauro Carvalho Chehab
2016-08-25 16:12 ` David Carroll
2016-08-25 20:46 ` Steven French
2016-08-25 20:58 ` Greg KH
2016-08-26  0:33   ` Joe Perches
2016-08-26 12:59 ` Shuah Khan
2016-08-26 16:56 ` Florian Fainelli
2016-08-26 17:09   ` Joe Perches
2016-08-26 19:34 ` Jason Baron
2016-08-26 19:50   ` Joe Perches
2016-08-26 20:05     ` Borislav Petkov
2016-08-26 20:17       ` Luck, Tony
2016-09-01 12:58         ` Borislav Petkov
2016-09-01 16:02           ` Joe Perches
2016-09-02  5:26             ` Borislav Petkov
     [not found] ` <CACwGpODqLAjQxgw=EdtWCKhFywy9btv9Ka6XG8YXbzKEBFPzEg@mail.gmail.com>
2016-08-28  2:40   ` Joe Perches
2016-08-30 15:19 ` Anders Larsen
2016-08-30 15:35   ` Joe Perches
  -- strict thread matches above, loose matches on Subject: below --
2016-08-25 10:00 Tigran Aivazian
2016-08-25 10:09 ` Joe Perches
2016-08-24 23:33 Joe Perches

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=1472084663.3746.234.camel@perches.com \
    --to=joe@perches.com \
    --cc=linux-graphics-maintainer@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petr@vandrovec.name \
    --cc=petr@vmware.com \
    --cc=pv-drivers@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.