From: nick <yocto6@gmail.com>
To: David Lang <david@lang.hm>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Help Out and Issues with the Community
Date: Fri, 26 Sep 2014 15:26:54 -0400 [thread overview]
Message-ID: <5425BDFE.6050908@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409251914420.28845@nftneq.ynat.uz>
On 14-09-25 10:20 PM, David Lang wrote:
>> Hello Developers,
>> For the last week or two I have been trying to contact people for help and/or learning in order to help out
>> more. I am unable to get any emails back from them, I am assuming this is due to my issues with the community.
>> If someone would like to explain a way to either resolve this or help me me learn the community rules and how
>> to do things the right way that would be great.
>
> Going over the archives a bit, it looks like there are a lot of people who have taken the time to reply to you.
>
> It looks like you are falling into a common trap of looking at particular bug reports or FIXME items and trying to silence them. But you are doing so without understanding the code or functionality being provided. As a result, you are doing exactly what people are afraid that static checking will result in, a local fix to silence the checker that doesn't actually fix the overall problem.
>
> In addition to the various places you've already been pointed at, I'd suggest that you look at the kernel janitors pages and mailing list (http://kernelnewbies.org/KernelJanitors), the linux-kernel list has a huge membership and a high volume of traffic, so learning as you work here is not always the best thing to do.
>
> David Lang
David,
That wasn't my idea, it was to help out and ask questions if I don't understand something first. I will start with kernel janitors and go from their.
Thanks Nick
next prev parent reply other threads:[~2014-09-26 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 1:02 Help Out and Issues with the Community nick
2014-09-26 2:20 ` David Lang
2014-09-26 19:26 ` nick [this message]
2014-09-27 14:59 ` Sudip Mukherjee
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=5425BDFE.6050908@gmail.com \
--to=yocto6@gmail.com \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
/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