All of lore.kernel.org
 help / color / mirror / Atom feed
From: berk walker <berk@panix.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: neilb@suse.de, linux-raid@vger.kernel.org
Subject: Re: Stable versions of mdadm ...
Date: Sat, 20 Sep 2008 21:24:43 -0400	[thread overview]
Message-ID: <48D5A25B.7050402@panix.com> (raw)
In-Reply-To: <48D59E64.5060707@tmr.com>

Bill Davidsen wrote:
> berk walker wrote:
>> Neil - is there an history file of "Stable" mdadm releases?  or are 
>> there any?  I would trust YOU [and yours] more than canned firmware.
>>
> With one exception long ago I don't think I would regard any as 
> "unstable." Regular updates do show up, of course, but unless you are 
> doing something really unusual you should have no issues. Usually the 
> one the distribution ships is well tested, so unless you need some 
> very recent feature there's no need for the bleeding edge.
>> 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.
>
I should have said versions/releases vs. kernel levels.  And Bill - - 
90% of this newsgroup/forum IS either about what is "broke" or patches 
to fix it.  Sir, I have been here for YEARS.  And I have NO intention to 
say anything which might be taken as detrimental or negative here.  I 
said have - I meant had, eh?

Mea culpa.
b-

  reply	other threads:[~2008-09-21  1:24 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 ` Stable versions of mdadm berk walker
2008-09-21  1:07   ` Bill Davidsen
2008-09-21  1:24     ` berk walker [this message]
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=48D5A25B.7050402@panix.com \
    --to=berk@panix.com \
    --cc=davidsen@tmr.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.