From: philipp.muhoray@gmail.com (Philipp Muhoray)
To: kernelnewbies@lists.kernelnewbies.org
Subject: A quick guide to why stand-alone checkpatch patches suck...
Date: Wed, 17 Sep 2014 20:01:02 +0200 [thread overview]
Message-ID: <5419CC5E.3090803@gmail.com> (raw)
In-Reply-To: <CAPDOMVhQ06fW0k9aAeqeNnQBokyqVuWeiEu09MHJyUEZ6xjd1Q@mail.gmail.com>
Am 2014-09-17 19:47, schrieb Nick Krause:
> On Wed, Sep 17, 2014 at 1:13 PM, Bruno Guedes Souto
> <brunoguedes@gmail.com> wrote:
>> This was a great discussion, until you guys started feeding the troll again.
>>
>> Can we just stop feeding the troll? He will prob go way...
>>
>> If every *single* time that Nick posts something you reply to him it will only
>> lead to more replies from him saying he will get better, understand what he is
>> doing and that he wants to improve his rep with the community. That's his
>> standard speech.
>>
>> BGS
>>
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> Can I stop being called a troll. I am trying to learn here and improve
> my rep and understanding of
> the kernel. I would like to help but with this negative light around
> me it is much more difficult and
> hard to do. I understand the problems I have caused now and would like
> to improve my rep with
> a tutor or someone who is willing to be my router to the community
> until I improve enough to a
> member of the community on my own.
> Thanks Nick
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Why do you think that some stranger on the internet is going to be your
tutor? Unless you belong to some minority, you shouldn't be waiting for
a tutor to take your hand and guide you... that's probably not going to
happen. Apply the advice that's been already given to you, e.g. read the
old mails and write each advice down. Until that, *please* lurk moar.
next prev parent reply other threads:[~2014-09-17 18:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 0:25 A quick guide to why stand-alone checkpatch patches suck Valdis Kletnieks
2014-09-17 0:37 ` Greg KH
2014-09-17 1:35 ` Greg Donald
2014-09-17 3:42 ` Valdis.Kletnieks at vt.edu
2014-09-17 4:56 ` Greg KH
2014-09-17 5:43 ` Sudip Mukherjee
2014-09-17 10:39 ` Robert P. J. Day
2014-09-17 11:20 ` Robert P. J. Day
2014-09-17 11:38 ` nick
2014-09-17 11:51 ` Sudip Mukherjee
2014-09-17 11:53 ` nick
2014-09-17 12:05 ` Greg Freemyer
2014-09-17 12:09 ` nick
2014-09-17 12:17 ` Kai Bojens
2014-09-17 12:23 ` nick
2014-09-17 12:25 ` Greg Freemyer
2014-09-17 12:29 ` Nick Krause
2014-09-17 14:39 ` Valdis.Kletnieks at vt.edu
2014-09-17 11:53 ` Robert P. J. Day
2014-09-17 11:55 ` nick
2014-09-17 12:17 ` Chris Lee
2014-09-17 12:19 ` nick
2014-09-17 11:56 ` Greg Freemyer
2014-09-17 12:00 ` Robert P. J. Day
2014-09-17 12:05 ` nick
2014-09-17 12:02 ` nick
2014-09-17 14:39 ` Valdis.Kletnieks at vt.edu
2014-09-17 17:04 ` Nick Krause
2014-09-17 17:13 ` Bruno Guedes Souto
2014-09-17 17:47 ` Nick Krause
2014-09-17 18:01 ` Philipp Muhoray [this message]
2014-09-17 18:14 ` Nick Krause
2014-09-17 18:15 ` Robert P. J. Day
2014-09-17 18:44 ` Nick Krause
2014-09-17 20:45 ` John de la Garza
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=5419CC5E.3090803@gmail.com \
--to=philipp.muhoray@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.