From: berk walker <berk@panix.com>
Cc: neilb@suse.de, linux-raid@vger.kernel.org
Subject: Stable versions of mdadm ...
Date: Sat, 20 Sep 2008 20:28:51 -0400 [thread overview]
Message-ID: <48D59543.3040203@panix.com> (raw)
In-Reply-To: <yq1y71mmjvw.fsf@sermon.lab.mkp.net>
Neil - is there an history file of "Stable" mdadm releases? or are
there any? I would trust YOU [and yours] more than canned firmware.
Hey - you should buy US, the $ [USD] isn't worth squat - this is the 1st
time in my memory [I'm 65] that we actually don't have a trade deficit.
berk
next prev parent reply other threads:[~2008-09-21 0:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 0:18 [PATCH] md: Add support for data integrity to MD Martin K. Petersen
2008-09-21 0:26 ` Dan Williams
2008-09-21 2:01 ` Martin K. Petersen
2008-09-21 0:28 ` berk walker [this message]
2008-09-21 1:07 ` Stable versions of mdadm Bill Davidsen
2008-09-21 1:24 ` berk walker
2008-09-24 2:46 ` [PATCH] md: Add support for data integrity to MD Neil Brown
2008-09-29 14:51 ` Martin K. Petersen
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=48D59543.3040203@panix.com \
--to=berk@panix.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 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).