All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: Igor M Podlesny <for.poige+lsr@gmail.com>
Cc: Roman Mamedov <rm@romanrm.ru>, NeilBrown <neilb@suse.de>,
	linux-raid@vger.kernel.org
Subject: Re: "mdadm: Raid level 5 not permitted with --build" -- why is that?
Date: Mon, 25 Jun 2012 14:40:15 +0200	[thread overview]
Message-ID: <4FE85C2F.5050007@hesbynett.no> (raw)
In-Reply-To: <CA+sTkh7Tv-F2fofWviF+X+Kp5-RLWmkTZveB6+jDHewLhhK50Q@mail.gmail.com>

On 25/06/2012 14:12, Igor M Podlesny wrote:
> On 25 June 2012 19:58, Roman Mamedov <rm@romanrm.ru> wrote:
>> On Mon, 25 Jun 2012 19:33:23 +0800
>> Igor M Podlesny <for.poige+lsr@gmail.com> wrote:
>>
>>>> Feel free to send a patch.
>>>
>>>     — "Feel free" to spend time digging into an area which isn't what
>>> you get paid for? At least what exactly should be patched this time,
>>> will you kindly tell us?
>>
>> Oh come on, that's just rude. I don't think Neil is paid by anyone to answer
>> your questions here either.
>
>     Neither he was paid to add his "feel free", I guess, was he? Or was
> that such an intricate payment?
>

Like many pieces of open source software, Linux md raid is written and 
maintained by a mixture of volunteer work and corporate sponsorship.  I 
have no idea how much Suse (or Novell) pay Neil for the work he does - 
but he goes far beyond the call of duty in his support work on this 
mailing list.  All he asks is that you ask your questions in a clear and 
polite way.  Putting the question in the subject but not in the body of 
the email is not good enough - the post should have a good subject line 
/and/ a good email body.  Why should Neil or anyone else take the time 
to write a helpful reply to someone who cannot even be bothered to write 
a good email?

Neil told you why md raid does not (currently) implement "--build" for 
raid5.  And he suggested that if you want that behaviour to change, you 
are always welcome to send a patch.  If you don't want to write an 
implementation of the missing behaviour, that's fair enough too - very 
few people respond to "feel free to send a patch" by actually sending a 
patch.  But if you want to get annoyed and sarcastic, please keep your 
comments to yourself.

mvh.,

David



--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-06-25 12:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22  3:07 "mdadm: Raid level 5 not permitted with --build" -- why is that? Igor M Podlesny
2012-06-25  6:52 ` NeilBrown
2012-06-25 11:33   ` Igor M Podlesny
2012-06-25 11:58     ` Roman Mamedov
2012-06-25 12:12       ` Igor M Podlesny
2012-06-25 12:40         ` David Brown [this message]
2012-06-25 13:10           ` Igor M Podlesny
2012-06-25 13:14             ` Rudy Zijlstra
2012-06-25 13:17               ` Igor M Podlesny
2012-06-25 17:59                 ` John Crisp
2012-06-26  1:57                   ` Igor M Podlesny
2012-06-26 11:55                     ` John Crisp
2012-06-26  1:13             ` NeilBrown
2012-06-26  2:22               ` Igor M Podlesny

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=4FE85C2F.5050007@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --cc=for.poige+lsr@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=rm@romanrm.ru \
    /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.