linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Sage Weil <sage@newdream.net>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeff Layton <jlayton@kernel.org>
Subject: Re: linux-next: new contact(s) for the ceph tree?
Date: Mon, 11 May 2020 07:08:06 +1000	[thread overview]
Message-ID: <20200511070806.397e0584@canb.auug.org.au> (raw)
In-Reply-To: <CAOi1vP8JjtBZoy0zAgz7=wwMuHiiRPCvxz7ZKicE9nh-NZXz2Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

Hi Ilya,

On Sun, 10 May 2020 09:40:07 +0200 Ilya Dryomov <idryomov@gmail.com> wrote:
>
> On Sat, May 9, 2020 at 5:47 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Sat, 9 May 2020 01:03:14 +0000 (UTC) Sage Weil <sage@newdream.net> wrote:  
> > >
> > > Jeff Layton <jlayton@kernel.org>  
> >
> > Done.  
> > > On Sat, 9 May 2020, Stephen Rothwell wrote:  
> > > >
> > > > I noticed commit
> > > >
> > > >   3a5ccecd9af7 ("MAINTAINERS: remove myself as ceph co-maintainer")
> > > >
> > > > appear recently.  So who should I now list as the contact(s) for the
> > > > ceph tree?  
> 
> I thought maintainers were on the list automatically.  If there is
> a separate list, please add me as well.

Done.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-05-10 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 23:45 linux-next: new contact(s) for the ceph tree? Stephen Rothwell
2020-05-09  1:03 ` Sage Weil
2020-05-09  3:47   ` Stephen Rothwell
2020-05-10  7:40     ` Ilya Dryomov
2020-05-10 21:08       ` Stephen Rothwell [this message]

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=20200511070806.397e0584@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=idryomov@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sage@newdream.net \
    /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;
as well as URLs for NNTP newsgroup(s).