From: Jeff Layton <jlayton@redhat.com>
To: Christoph Hellwig <hch@lst.de>, ooo@electrozaur.com, bhalevy@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH, RFC] MAINTAINERS: update OSD entries
Date: Tue, 02 May 2017 07:33:32 -0400 [thread overview]
Message-ID: <1493724812.2715.1.camel@redhat.com> (raw)
In-Reply-To: <20170502075720.23570-1-hch@lst.de>
On Tue, 2017-05-02 at 09:57 +0200, Christoph Hellwig wrote:
> The open-osd domain doesn't exist anymore, and mails to the list lead
> to really annoying bounced that repeat every day.
>
> Also the primarydata address for Benny bounces, and while I have a new
> one for him he doesn't seem to be maintaining the OSD code any more.
>
> Which beggs the question: should we really leave the Supported status
> in MAINTAINERS given that the code is barely maintained?
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> MAINTAINERS | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1bb06c5f7716..28dd83a1d9e2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9418,10 +9418,6 @@ F: drivers/net/wireless/intersil/orinoco/
>
> OSD LIBRARY and FILESYSTEM
> M: Boaz Harrosh <ooo@electrozaur.com>
> -M: Benny Halevy <bhalevy@primarydata.com>
> -L: osd-dev@open-osd.org
> -W: http://open-osd.org
> -T: git git://git.open-osd.org/open-osd.git
> S: Maintained
> F: drivers/scsi/osd/
> F: include/scsi/osd_*
Hah, you beat me to it! I was going to spin up a patch for this today.
Acked-by: Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2017-05-02 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 7:57 [PATCH, RFC] MAINTAINERS: update OSD entries Christoph Hellwig
2017-05-02 11:33 ` Jeff Layton [this message]
2017-05-03 10:08 ` Boaz Harrosh
2017-05-03 17:01 ` Benny Halevy
2017-05-09 1:43 ` Martin K. Petersen
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=1493724812.2715.1.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=bhalevy@gmail.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ooo@electrozaur.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.