From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Bad Patches and Issues with other devolopers
Date: Wed, 6 Aug 2014 09:35:09 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408060928250.6279@localhost> (raw)
In-Reply-To: <CAPDOMVhGFep4wm3+eu=qcznVsohF-seLiiQQJFdLZ7aQFUvX_g@mail.gmail.com>
On Wed, 6 Aug 2014, Nick Krause wrote:
> Seems I am banned from the [LKML] list is there any way around this
> or not?
good lord, man ... when you're *banned* from a particular venue, the
proper and productive response is to examine your behaviour, then do
what it takes to correct it, *not* immediately ask if there's a way
to circumvent the ban.
at this point, i suggest it's time to ban you from *this* list for
the simple reason that your participation has nothing to do with
furthering anyone's knowledge of the linux kernel; rather, it has
devolved into a discussion about your unacceptable behaviour, and this
is most emphatically *not* the proper mailing list for that.
if there's a voting process, i would vote that nick krause be
removed from this mailing list.
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-08-06 13:35 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 [this message]
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
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=alpine.LFD.2.11.1408060928250.6279@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).