From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.com>
Cc: Artur Paszkiewicz <artur.paszkiewicz@intel.com>,
linux-raid@vger.kernel.org, dm-devel@redhat.com,
LKML <linux-kernel@vger.kernel.org>, Shaohua Li <shli@kernel.org>
Subject: Re: WANTED new maintainer for Linux/md (and mdadm)
Date: Tue, 02 Feb 2016 07:19:58 -0500 [thread overview]
Message-ID: <wrfjoabz1ez5.fsf@redhat.com> (raw)
In-Reply-To: <87powo2ber.fsf@notabene.neil.brown.name> (NeilBrown's message of "Wed, 27 Jan 2016 10:01:16 +1100")
NeilBrown <neilb@suse.com> writes:
> On Wed, Jan 20 2016, Artur Paszkiewicz wrote:
>>
>> Hi Neil,
>>
>> Thank you for your work and time spent on maintaining MD/mdadm. I would also
>> like to offer help for the emerging maintainership team. I've been
>> working with
>> MD RAID for more than 4 years, mostly testing and developing the IMSM-related
>> parts on behalf of my employer - Intel. I realize that I was not very visible
>> on this mailing list, but I think I have a pretty good knowledge about mdadm
>> and the MD drivers. Now I have Intel's approval to take on maintaining MD RAID
>> as part of my job, not focusing primarily on IMSM. I definitely feel more
>> confident with maintaining mdadm, but I would certainly like to learn more
>> about the kernel MD stack and help with it as much as I can.
>
> Hi Arthur,
> thanks for all your IMSM work over the years! It is great that you can
> continue contributing and do so more broadly.
>
> For the moment Jes Serensen will be co-ordinating mdadm (once I make a
> release ... tomorrow?) and Shaohua Li will be looking after the
> kernel/md side. I'm sure there is plenty of room for you too though.
> Only one person (at a time) can queue patches, but several can
> collaborate at development and support and bug fixing and testing and
> ....
> I suggest you find ways to co-ordinate with them.
>
> This:
> https://bugzilla.kernel.org/show_bug.cgi?id=108741
> is currently most important in my mind, but there are other things to
> do.
Hi Arthur,
I have setup a git repository for mdadm here:
git://git.kernel.org/pub/scm/utils/mdadm/mdadm.git
I'll be relying heavily on your contributions in managing this now that
Neil is leaving it to us. I'll do my best to maintain it in a similar
manner to Neil, albeit I am probably going to screw up a lot more often.
Please fire away those patches and do not be afraid to yell at me if I
get something wrong!
Cheers,
Jes
prev parent reply other threads:[~2016-02-02 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 6:10 NeilBrown
2015-12-21 12:28 ` Phil Turmel
2016-01-04 10:16 ` [dm-devel] " Sebastian Parschauer
2016-01-04 18:24 ` Shaohua Li
2016-01-08 2:38 ` NeilBrown
2016-01-04 20:40 ` [dm-devel] " Brassow Jonathan
2016-01-06 16:53 ` Jes Sorensen
2016-01-08 2:17 ` NeilBrown
2016-01-08 20:28 ` Jes Sorensen
2016-01-20 8:27 ` Artur Paszkiewicz
2016-01-26 23:01 ` NeilBrown
2016-02-02 12:19 ` Jes Sorensen [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=wrfjoabz1ez5.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=artur.paszkiewicz@intel.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=shli@kernel.org \
/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
Powered by JetHome