All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: NeilBrown <neilb@suse.com>, linux-raid@vger.kernel.org
Subject: Raid wiki - was Re: MDADM grow /dev/md0 - chunk size
Date: Wed, 25 Jan 2017 17:04:48 +0000	[thread overview]
Message-ID: <5888DAB0.3070905@youngman.org.uk> (raw)
In-Reply-To: <87lgu2emgs.fsf@notabene.neil.brown.name>

On 22/01/17 22:52, NeilBrown wrote:
> And... please don't send nag emails so soon - it was barely more than
> 24hours after the original.  This just comes across as rude and
> impatient.  People have other commitments.
> My rule of thumb is to wait at least a week before resending - and then
> resend the full text of the original.  Your nag email was not only too
> soon, but contained no detail and so was useless.

Just to point out - to everyone :-) - that the linux wiki is currently
being maintained so pointing people at it is a good idea.

And there's a page called "asking for help". Not only does this tell
people all the commands (like "cat /proc/mdstat", "mdadm --detail",
"mdadm --examine") they should be running to get the info the list is
likely to want, but

*almost the first thing* on that page is a reminder that many of us here
are volunteers, and prompt replies are a privilege not a right. Lusers
get spoilt in that we take pride in our work.

But can I ask, if you do point people at the wiki, just take a quick
glance yourself first. And if you do spot a mistake on the wiki,
brickbats and fixes are welcome :-)

Cheers,
Wol

      reply	other threads:[~2017-01-25 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15 10:33 MDADM grow /dev/md0 - chunk size J. Cassidy
2017-01-22 22:52 ` NeilBrown
2017-01-25 17:04   ` Wols Lists [this message]

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=5888DAB0.3070905@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.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.