From: NeilBrown <neilb@suse.de>
To: linux RAID <linux-raid@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
Doug Ledford <dledford@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
Dan Williams <dan.j.williams@intel.com>,
"Dorau, Lukasz" <lukasz.dorau@intel.com>,
"Czarnowska, Anna" <anna.czarnowska@intel.com>,
Przemyslaw Czarnowski
<przemyslaw.hawrylewicz.czarnowski@intel.com>,
Clint Byrum <clint@ubuntu.com>
Subject: Last call for input to mdadm-3.2.4
Date: Thu, 3 May 2012 14:22:01 +1000 [thread overview]
Message-ID: <20120503142201.649766de@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hi all,
I hope to release mdadm-3.2.4 next week.
This is mostly a bugfix release though there are a few small features
like "--prefer=" which guides the selection of the device names reported by
--detail and --monitor.
It also now defaults /run/mdadm for runtime files rather than /dev/.mdadm or
/var/run/mdadm.
I hope it will be just what I currently have in the 'master' branch of my git
tree, plus changes to the version numbers. However if anyone has anything
that they really want to go in *now* I'm open to contributions if they are
important.
I'll then try to focus more on preparing for 3.3 which will include:
- badblock log support
- hot-replace support
- raid10 reshape
and maybe other stuff.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2012-05-03 4:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 4:22 NeilBrown [this message]
2012-05-03 9:18 ` Last call for input to mdadm-3.2.4 Jes Sorensen
2012-05-15 11:50 ` mdadm-3.2.5 coming soon :-( NeilBrown
2012-05-15 15:22 ` Maciej Naruszewicz
2012-05-17 5:44 ` NeilBrown
2012-05-17 8:28 ` Patelczyk, Maciej
2012-05-17 11:52 ` Patelczyk, Maciej
2012-05-18 3:44 ` 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=20120503142201.649766de@notabene.brown \
--to=neilb@suse.de \
--cc=Jes.Sorensen@redhat.com \
--cc=anna.czarnowska@intel.com \
--cc=clint@ubuntu.com \
--cc=dan.j.williams@intel.com \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
--cc=mjt@tls.msk.ru \
--cc=przemyslaw.hawrylewicz.czarnowski@intel.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 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).