From: xerofoify@gmail.com (Nick Krause)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Bad Patches and Issues with other devolopers
Date: Wed, 6 Aug 2014 14:08:36 -0400 [thread overview]
Message-ID: <CAPDOMVg0WCEwYHc6+MNcLeRHPrTO6iLOwVP4FZ7t63x_wAkFSA@mail.gmail.com> (raw)
In-Reply-To: <CAPDOMVgNuftJmeEVNGHzfmjBYfgMX_HiMDk2dcCW2epxCwKDvA@mail.gmail.com>
On Wed, Aug 6, 2014 at 2:05 PM, Nick Krause <xerofoify@gmail.com> wrote:
> On Wed, Aug 6, 2014 at 1:24 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>> On Wed, 6 Aug 2014, Valdis.Kletnieks at vt.edu wrote:
>>
>>> On Wed, 06 Aug 2014 10:48:14 +0100, Anuz Pratap Singh Tomar said:
>>>
>>> > oh man you have gained prominence in vger?
>>> > They have banned you from vger.
>>>
>>> Wow. I've been around for a dozen years or so, and can't remember
>>> *that* ever happening before. That takes some *major* doing, and
>>> could take literally years to straighten out. How to approach that?
>>
>> *sigh* ... the fact that nick has, *single-handedly*, pissed off and
>> wasted the time of numerous subsystem maintainers to the point where
>> he has been banned from LKML and has, in addition, *single-handedly*
>> turned the kernel newbies mailing list into his personal self-help
>> playground means that he needs to be shown the door.
>>
>> i don't want to sound unsympathetic, but it doesn't *matter* if this
>> is nick's fault or not -- he is, quite simply, a disruptive influence
>> and is, at the moment, turning this mailing list into chaos.
>>
>> people are asking, can he be salvaged? to which the proper answer
>> is, who cares? there are a *lot* of kernel newbies out there who would
>> desperately like to get to the point where *they* can start submitting
>> patches, and most of *those* people are willing to read and listen and
>> follow the advice of the veterans to the point where they become
>> useful contributors. nick is not.
>>
>> it's massively ironic that countless people have told nick what he
>> should be doing, to which his inveitable response is, "ok, but what
>> should i be doing?"
>>
>> if you want to help nick, knock yourself out but take it offline.
>> nick has already wasted far too much bandwidth that could have been
>> invested in helping newbies that are willing to *listen*.
>>
>> rday
>>
>> --
>>
>> ========================================================================
>> Robert P. J. Day Ottawa, Ontario, CANADA
>> http://crashcourse.ca
>>
>> Twitter: http://twitter.com/rpjday
>> LinkedIn: http://ca.linkedin.com/in/rpjday
>> ========================================================================
>>
>
> Robert,
> I am trying to listen now and this was my fault.
> Regards Nick
Also Robert I starting this the wrong way be treating this as a
playground rather then
for real work and that was another mistake I made. I do feel that if
you guys give me
a second case I will listen much better and stop wasting time.
Regards Nick
next prev parent reply other threads:[~2014-08-06 18:08 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 17:42 Bad Patches and Issues with other devolopers Nick Krause
2014-08-05 17:56 ` Kristofer Hallin
2014-08-05 17:59 ` Mandeep Sandhu
2014-08-05 18:04 ` Nick Krause
2014-08-05 18:28 ` Anuz Pratap Singh Tomar
2014-08-05 18:25 ` Sudip Mukherjee
2014-08-05 19:52 ` Rohan Puri
2014-08-05 19:54 ` Valdis.Kletnieks at vt.edu
2014-08-05 20:20 ` Nick Krause
[not found] ` <alpine.LFD.2.11.1408051702460.26301@localhost>
2014-08-05 21:35 ` Nick Krause
2014-08-05 22:49 ` Greg Freemyer
2014-08-05 23:43 ` Nick Krause
2014-08-06 9:48 ` Anuz Pratap Singh Tomar
2014-08-06 10:02 ` Pramod Gurav
2014-08-06 10:30 ` Anuz Pratap Singh Tomar
2014-08-06 12:47 ` Nick Krause
2014-08-06 13:25 ` Nick Krause
2014-08-06 13:28 ` Kristofer Hallin
2014-08-06 13:32 ` Nick Krause
2014-08-06 13:45 ` Sudip Mukherjee
2014-08-06 13:46 ` Anuz Pratap Singh Tomar
2014-08-06 13:56 ` Nick Krause
2014-08-06 13:59 ` Andev
2014-08-06 14:07 ` Nick Krause
2014-08-06 14:22 ` Nick Krause
2014-08-06 14:30 ` Kristofer Hallin
2014-08-06 13:35 ` Robert P. J. Day
2014-08-06 16:31 ` Josh Carlson
2014-08-06 16:47 ` Nick Krause
2014-08-06 17:11 ` Greg Freemyer
2014-08-06 17:16 ` Nick Krause
2014-08-06 16:52 ` Mandeep Sandhu
2014-08-06 16:58 ` Nick Krause
2014-08-06 16:58 ` Valdis.Kletnieks at vt.edu
2014-08-06 17:03 ` Nick Krause
2014-08-06 17:24 ` Robert P. J. Day
2014-08-06 18:05 ` Nick Krause
2014-08-06 18:08 ` Nick Krause [this message]
2014-08-06 18:30 ` Lidza Louina
2014-08-06 18:33 ` Nick Krause
2014-08-06 18:42 ` Lidza Louina
2014-08-06 18:45 ` Nick Krause
2014-08-06 18:53 ` Kristofer Hallin
2014-08-06 18:56 ` Nick Krause
2014-08-06 20:45 ` StephanT
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=CAPDOMVg0WCEwYHc6+MNcLeRHPrTO6iLOwVP4FZ7t63x_wAkFSA@mail.gmail.com \
--to=xerofoify@gmail.com \
--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).