From: Dan Williams <dan.j.williams@intel.com>
To: "neilb@suse.de" <neilb@suse.de>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Labun, Marcin" <Marcin.Labun@intel.com>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
Ignacy Kasperowicz <ignacy.kasperowicz@intel.com>
Subject: Re: [mdadm PATCH 0/2] two 3.1.3 regression fixes (incremental assembly)
Date: Tue, 10 Aug 2010 16:40:46 -0700 [thread overview]
Message-ID: <4C61E37E.4060403@intel.com> (raw)
In-Reply-To: <20100810164551.26691.17944.stgit@localhost.localdomain>
On 8/10/2010 9:46 AM, Williams, Dan J wrote:
> Hi Neil,
>
> The mdadm -I --no-degraded option needs to be acceptable for some time
> to come, do you have a policy for when deprecated options can be scheduled for
> removal? The error code for -I shall be zero in the 'not enough' case to
> restore the correct and established pre-3.1.3 behavior.
>
> Also available via git:
>
> git://github.com/djbw/mdadm.git master
>
> ---
>
> Dan Williams (2):
> Incremental: return success in 'container not enough' case
> Incremental: accept '--no-degraded' as a deprecated option
Note, both of these should have been tagged:
Reported-by: Ignacy Kasperowicz <ignacy.kasperowicz@intel.com>
If you take the patches directly.
Thanks,
Dan
next prev parent reply other threads:[~2010-08-10 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 16:46 [mdadm PATCH 0/2] two 3.1.3 regression fixes (incremental assembly) Dan Williams
2010-08-10 16:46 ` [mdadm PATCH 1/2] Incremental: return success in 'container not enough' case Dan Williams
2010-08-10 16:46 ` [mdadm PATCH 2/2] Incremental: accept '--no-degraded' as a deprecated option Dan Williams
2010-08-10 23:40 ` Dan Williams [this message]
2010-08-12 1:22 ` [mdadm PATCH 0/2] two 3.1.3 regression fixes (incremental assembly) Neil Brown
2010-08-12 1:47 ` Neil Brown
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=4C61E37E.4060403@intel.com \
--to=dan.j.williams@intel.com \
--cc=Marcin.Labun@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=ignacy.kasperowicz@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.