From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Improve my Rep
Date: Mon, 15 Sep 2014 12:36:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1409151227190.7850@localhost> (raw)
In-Reply-To: <CAPDOMVheNt8tz8htrYqfgB74QLT-1tzevwtGsQTas4uVyBOKyQ@mail.gmail.com>
On Mon, 15 Sep 2014, Nick Krause wrote:
> On Mon, Sep 15, 2014 at 11:16 AM, Anuz Pratap Singh Tomar
> <chambilkethakur@gmail.com> wrote:
> >
> >
> > On Mon, Sep 15, 2014 at 3:38 PM, Nick Krause <xerofoify@gmail.com> wrote:
> >>
> >> After issues with the community I am wondering how to improve my rep
> >> and help out more.
> >> I will start out with check patch but if there is other work please
> >> let me known :).
> >>
> > Seriously, you are beyond help.
> > A lot of people have tried to answer your mails, correct your patches and
> > give you correct advice, but you choose to ignore all of that.
> > This behaviour qualifies as either a) Trolling or b) you need medical
> > help(as a lot of people pointed out on LKML).
> > So please seriously stop, I am not sure what are you trying to achieve by
> > posting here, but it is just noise and annoyance to everyone.
> >
> > --
> > Thank you
> > Warm Regards
> > Anuz
> I am sure I can help. Seems I need to be more careful with my patches.
> Nick
but this is what you say every single time, without fail, and it's
at the point where i don't believe you actually read what other people
have written. regardless of the excruciating detail from others about
the crappiness of your "patches", your reply is generally little more
than, "i guess i better test my patches more. thanks for the info."
then you go off, f**k things up even worse, submit more garbage,
people take the time to point that out, again in excruciating detail,
to which you invariably respond (yet again), "gee, i guess i really
should test my patches more. thanks for your patience." and on and on
and on. sometimes, inexplicably, you even add a smiley face as if this
is amusing on some level.
you never show contrition or even the slightest hint of remorse for
screwing things up as badly as you do, and wasting everyone's time. in
the face of mounting frustration with your incompetence, it's always,
"gosh, i guess i better test my patches more. thanks for the info."
and the cycle continues ...
prediction? if nick responds to this message, well, you know what i
think he's going to say. le *sigh* ...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-09-15 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 14:38 Improve my Rep Nick Krause
2014-09-15 14:48 ` Greg Freemyer
2014-09-15 14:54 ` Valdis.Kletnieks at vt.edu
2014-09-15 15:16 ` Anuz Pratap Singh Tomar
2014-09-15 15:22 ` Nick Krause
2014-09-15 16:03 ` Valdis.Kletnieks at vt.edu
2014-09-15 16:36 ` Robert P. J. Day [this message]
2014-09-15 17:54 ` Raphael Philipe
2014-09-15 19:02 ` Robert P. J. Day
2014-09-15 21:13 ` Jake Campbell
2014-09-15 22:01 ` Valdis.Kletnieks at vt.edu
2014-09-16 7:46 ` Bernd Petrovitsch
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=alpine.LFD.2.11.1409151227190.7850@localhost \
--to=rpjday@crashcourse.ca \
--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).