kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Filtering noise is about protecting resourses
Date: Tue, 09 Dec 2014 13:27:26 -0500	[thread overview]
Message-ID: <8448.1418149646@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 09 Dec 2014 06:33:07 -0500." <5486DDF3.6090401@gmail.com>

On Tue, 09 Dec 2014 06:33:07 -0500, nick said:
> I understand that now after reading your message.

Sorry Nick.  You might believe that, but nobody else does at this point. We've
heard that over and over for the last six months, and then you follow up with
behavior that indisputably proves that you either *didn't* understand, or
you totally didn't care.

> To be honest, I started out like this because I had no idea, where to start.
> If your willing to give me a place to start, that is of use I will be glad to
> help out.

I think that given your history, the best service you could do the Linux
community is to go work for a competitor.  The BSD's and Microsoft are
always looking for help.

Seriously Nick - whatever your motivations may be, Bj?rn is totally right.
Overall, you're a negative asset - I've personally submitted patches that
you've been trying to get submitted, *just so I didn't have to keep seeing
incorrect attempts*.  Now, FSM knows that there's been *tons* of times over the
past decade that I've spend 5, 10, even 20 times longer talking a newcomer
through getting a first patch accepted than it would have taken me to just
whomp one out myself and submit it.  The difference is that in those cases I
had a reasonable expectation that it would be a long-term win.

Let's face it Nick - there is no such expectation when you're concerned.
Avinash added the story of your most recent waste of Rafal's time.

At this point, I really see zero reason for anybody to remove your ban until
such time as you've demonstrated a long term (as in several years) ability
to do correct and productive development for some other project.  Because
quite frankly, until you fix whatever your problem is and become productive
on your own, we get less done while you're here than if you weren't.

And it's not our job to fix your problem.  It's your job.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20141209/5e1cb0d7/attachment.bin 

      reply	other threads:[~2014-12-09 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08  3:15 Remove Ban? nick
2014-12-08 15:32 ` Valdis.Kletnieks at vt.edu
2014-12-08 15:56   ` Nick Krause
2014-12-09  6:50     ` Avinash Patil
2014-12-09  7:56       ` Philipp Muhoray
2014-12-09  8:05         ` Sudip Mukherjee
2014-12-09  9:24         ` Filtering noise is about protecting resourses (was: Re: Remove Ban?) Bjørn Mork
2014-12-09 11:33           ` Filtering noise is about protecting resourses nick
2014-12-09 18:27             ` Valdis.Kletnieks at vt.edu [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=8448.1418149646@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).