kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (Nick Krause)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Bad Patches and Issues with other devolopers
Date: Tue, 5 Aug 2014 13:42:58 -0400	[thread overview]
Message-ID: <CAPDOMVhDMMAUxTv1zWMP=xWvqNCoCmhPC_970C2mAqf35kL1rg@mail.gmail.com> (raw)

I have sent out just ten bad patches and the developers seem very
annoyed with me and
think I am trolling. If someone on this list can find a way for me to
improve my relationship
with them and let me continue my work here that would be great.
Nick

             reply	other threads:[~2014-08-05 17:42 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 17:42 Nick Krause [this message]
2014-08-05 17:56 ` Bad Patches and Issues with other devolopers 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
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='CAPDOMVhDMMAUxTv1zWMP=xWvqNCoCmhPC_970C2mAqf35kL1rg@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).