From: Luca Berra <bluca@comedia.it>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Is there a good reason why I can't "mdadm -Gfn1 /dev/md1" ?
Date: Thu, 9 Jun 2005 13:20:55 +0200 [thread overview]
Message-ID: <20050609112055.GA26006@percy.comedia.it> (raw)
In-Reply-To: <17064.9218.919914.356958@cse.unsw.edu.au>
On Thu, Jun 09, 2005 at 09:12:02PM +1000, Neil Brown wrote:
>I'm very close to releasing mdadm 1.12.0. It will have this fixed.
do you have a prerelease, i'd like to test the stacking stuff.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2005-06-09 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 5:54 Is there a good reason why I can't "mdadm -Gfn1 /dev/md1" ? Piete Brooks
2005-06-09 6:07 ` Peter T. Breuer
2005-06-09 11:12 ` Neil Brown
2005-06-09 11:20 ` Luca Berra [this message]
2005-06-09 13:18 ` Neil Brown
2005-06-12 17:22 ` Stacked devices (Was: Is there a good reason why I can't "mdadm -Gfn1 /dev/md1" ?) Luca Berra
2005-06-14 0:59 ` Neil Brown
2005-06-09 11:40 ` Is there a good reason why I can't "mdadm -Gfn1 /dev/md1" ? Piete Brooks
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=20050609112055.GA26006@percy.comedia.it \
--to=bluca@comedia.it \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).