From: Sage Weil <sage@newdream.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ilya Dryomov <idryomov@gmail.com>,
Jeff Layton <jlayton@kernel.org>
Subject: Re: linux-next: new contact(s) for the ceph tree?
Date: Sat, 9 May 2020 01:03:14 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.21.2005090103060.29336@piezo.novalocal> (raw)
In-Reply-To: <20200509094515.7082eb92@canb.auug.org.au>
Jeff Layton <jlayton@kernel.org>
Thanks, Stephen!
sage
On Sat, 9 May 2020, Stephen Rothwell wrote:
> Hi all,
>
> 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?
>
> --
> Cheers,
> Stephen Rothwell
>
next prev parent reply other threads:[~2020-05-09 1:09 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 [this message]
2020-05-09 3:47 ` Stephen Rothwell
2020-05-10 7:40 ` Ilya Dryomov
2020-05-10 21:08 ` Stephen Rothwell
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=alpine.DEB.2.21.2005090103060.29336@piezo.novalocal \
--to=sage@newdream.net \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.