From: NeilBrown <neilb@suse.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Sergey B Kirpichev <skirpichev@gmail.com>,
linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Planning a bug-fix release for mdadm: mdadm 3.2.6
Date: Mon, 22 Oct 2012 09:01:21 +1100 [thread overview]
Message-ID: <20121022090121.68e958e5@notabene.brown> (raw)
In-Reply-To: <5082C6CE.9050809@msgid.tls.msk.ru>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
On Sat, 20 Oct 2012 19:44:14 +0400 Michael Tokarev <mjt@tls.msk.ru> wrote:
> On 20.10.2012 19:28, Michael Tokarev wrote:
> > On 18.10.2012 08:48, NeilBrown wrote:
> >> The "mdadm-3.2.x" branch of my git tree (git://neil.brown.name/mdadm)
> >> contains what I have so far. If anyone knows of bugs in current mdadm that
> >> really should be fixed for the next release and aren't in that tree, please
> >> let me know (or even send me a patch).
> >
> > There's apparently a small (but annoying when you hit it) bug mentioned in
> > http://bugs.debian.org/686703 -- when specifying --uuid, --homehost is NOT
> > ignored as it should be. I'm looking at it right now, so for now it is JFYI.
>
> I just sent a trivial one-liner patch for this issue. It is applicable for
> older releases too.
>
> And here's another trivial bugfix, now for spelling mistakes in various
> places, authred by Sergey Kirpichev (Cc'ed) and carried in debian mdadm
> package. Please consider applying.
>
> /mjt
I've applied these - thanks!
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-10-21 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 4:48 Planning a bug-fix release for mdadm: mdadm 3.2.6 NeilBrown
2012-10-20 15:28 ` Michael Tokarev
2012-10-20 15:44 ` Michael Tokarev
2012-10-21 22:01 ` NeilBrown [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=20121022090121.68e958e5@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=skirpichev@gmail.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).