From: Martin Wilck <mwilck@arcor.de>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Preparing for mdadm-3.3
Date: Thu, 27 Jun 2013 20:24:52 +0200 [thread overview]
Message-ID: <51CC8374.5070202@arcor.de> (raw)
In-Reply-To: <20130624171818.71a9688a@notabene.brown>
On 06/24/2013 09:18 AM, NeilBrown wrote:
> it has been way too long since an mdadm release. So I'm hoping to pull one
> together over the next few weeks. It will be mdadm-3.3
> My goal is to have it out by 25th July (i.e. one month).
I am preparing a relatively big patch set to get full support for
DDF/RAID10. I guess that will need to go in after 3.3, then.
Regards
Martin
next prev parent reply other threads:[~2013-06-27 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 7:18 Preparing for mdadm-3.3 NeilBrown
2013-06-24 13:44 ` Mark Knecht
2013-06-24 23:38 ` NeilBrown
[not found] ` <wrfjli5zfq1c.fsf@redhat.com>
2013-06-24 23:42 ` NeilBrown
2013-06-25 8:40 ` Jes Sorensen
2013-06-27 18:24 ` Martin Wilck [this message]
2013-07-01 23:41 ` NeilBrown
2013-07-25 8:02 ` NeilBrown
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=51CC8374.5070202@arcor.de \
--to=mwilck@arcor.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).