From: NeilBrown <neilb@suse.de>
To: linux RAID <linux-raid@vger.kernel.org>
Subject: Last call for mdadm-3.2.3.
Date: Thu, 15 Dec 2011 15:10:18 +1100 [thread overview]
Message-ID: <20111215151018.504ed1ce@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
Hi all,
I plan to release mdadm-3.2.3 sometime next week with whatever happens to be
in my 'master' branch at the time. And I'll try not to break it between now
and then. Then I'll open 3.3 devel properly.
So if anyone has a bug fix or other smallish issue they have been sitting on
for a while, now is a good time to let me know.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
reply other threads:[~2011-12-15 4:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111215151018.504ed1ce@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.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;
as well as URLs for NNTP newsgroup(s).