From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Get Back Into Kernel Work
Date: Sun, 15 Mar 2015 23:05:37 -0400 [thread overview]
Message-ID: <55064881.3030803@gmail.com> (raw)
In-Reply-To: <20150315164634.GC2338@www.mrbrklyn.com>
On 2015-03-15 12:46 PM, Ruben Safir wrote:
> On Sun, Mar 15, 2015 at 04:39:31PM +0000, Hugo Mills wrote:
>> On Sun, Mar 15, 2015 at 12:24:12PM -0400, Ruben Safir wrote:
>>> On Sun, Mar 15, 2015 at 05:16:27PM +0100, Levente Kurusa wrote:
>>>> On Sun, Mar 15, 2015 at 12:01:27PM -0400, Nicholas Krause wrote:
>>>>>>> [...]
>>>>> I was interested in Socs in staging as I believe there are a few
>>>>> would someone like to point me to one that I can get hardware for.
>
> Your 100% correct. I apologize
>
> Ruben
>
>
>>>>
>>>> Please read my message again. It should be YOU who does the research
>>>> about the work that YOU want to do, not us...
>>>
>>>
>>> I didn't write this. Are you intentionally trolling this?
>>
>> Nobody's claiming you did. This is a different thread to yours,
>> with a different subject line. Note that none of the quoted messages
>> above had your name as attribution.
>>
>>> The initial message under this subject had nothing to do with this.
>>> BTW - the atitiude is piss poor for what is SUPPOSED to be newbies area.
>>> Try taking some trips from Ernie and Fewer from Bert.
>>
>> This particular newbie (nick) has a reasonably long and ignoble
>> history in the kernel development area. He used up quite a lot of the
>> available polite late last summer, and isn't at the moment giving any
>> indications that he's made any improvements.
>>
>>> PS - no need to CC me when I'm reading the list.
>>
>> It's the default position on these mailing lists. You're generally
>> not going to have anyone remember that you don't want to be CC'd. A
>> message in your .sig to that effect might help, but it probably won't.
>>
>> Hugo.
>>
>> --
>> Hugo Mills | Be pure.
>> hugo at ... carfax.org.uk | Be vigilant.
>> http://carfax.org.uk/ | Behave.
>> PGP: 65E74AC0 | Torquemada, Nemesis
>
>
>
>>
Look I really do want to try and improve my rep as I really enjoy learning and programming
the kernel. I don't want to come up as I known everything I don't,all I am is some honest
criticism of where I am going wrong.
Nick
_______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
next prev parent reply other threads:[~2015-03-16 3:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 4:34 Get Back Into Kernel Work nick
2015-03-15 9:07 ` Robert P. J. Day
2015-03-15 12:28 ` Nicholas Krause
2015-03-15 12:55 ` Levente Kurusa
2015-03-15 15:48 ` Ruben Safir
2015-03-15 16:01 ` Nicholas Krause
2015-03-15 16:14 ` Sudip Mukherjee
2015-03-15 16:16 ` Nicholas Krause
2015-03-15 16:16 ` Levente Kurusa
2015-03-15 16:24 ` Ruben Safir
2015-03-15 16:39 ` Hugo Mills
2015-03-15 16:46 ` Ruben Safir
2015-03-16 3:05 ` nick [this message]
2015-03-15 17:16 ` Nicholas Krause
2015-03-23 13:51 ` el_es
2015-03-23 15:04 ` Nicholas Krause
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=55064881.3030803@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).