All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: o1bigtenor <o1bigtenor@gmail.com>
Cc: Adam Goryachev <mailinglists@websitemanagers.com.au>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Raid settings
Date: Mon, 29 Aug 2016 19:43:33 +0100	[thread overview]
Message-ID: <57C48255.5030006@youngman.org.uk> (raw)
In-Reply-To: <CAPpdf58qnEqobw8q1LTOAbT0MGRssV4HF2NO7a1-Mra8XnADkA@mail.gmail.com>

On 29/08/16 19:13, o1bigtenor wrote:
>> Once I've got access, I can sort out access for you, and if it works out
>> > well, we can work on this together :-) It'd be nice to get an up-to-date
>> > resource out there :-) Times move on, and the two original guys have
>> > moved on in their lives - now's as good a time as any to pass the baton :-)
>> >
> I'm starting to think that documents should be checked for
> 'currentness' at least
> annually if not more often. The software is constantly being worked on and
> hardware stuff is changing likely on a semi-annual basis.

Good sentiment. Snag is, the web is full of cobweb sites - and given the
propensity of the web to never forget, I don't think you're going to win
... It's like documentation - how many programmers keep documentation up
to date :-)

But yes, if it's (allegedly) hosted at kernel.org, yes it looks official
and should be kept up-to-date. And the reality is, a lot of it still is
good relevant advice. It's just the technical stuff, which isn't
actually the majority of the site. Unfortunately, if the tech stuff is
out of date, techies will distrust the rest.

Cheers,
Wol

  reply	other threads:[~2016-08-29 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 21:43 Raid settings o1bigtenor
2016-08-28 21:59 ` Wols Lists
2016-08-29  2:28   ` o1bigtenor
2016-08-29  2:46     ` Adam Goryachev
2016-08-29  9:26       ` o1bigtenor
2016-08-29 11:16         ` Wols Lists
2016-08-29 12:11           ` o1bigtenor
2016-08-29 12:19             ` Wols Lists
2016-08-29 18:13               ` o1bigtenor
2016-08-29 18:43                 ` Wols Lists [this message]
2016-08-29  6:18   ` Brad Campbell

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=57C48255.5030006@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=mailinglists@websitemanagers.com.au \
    --cc=o1bigtenor@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 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.