kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: el.es.cr@gmail.com (el_es)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Get Back Into Kernel Work
Date: Mon, 23 Mar 2015 13:51:30 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150323T144133-770@post.gmane.org> (raw)
In-Reply-To: 2A720F3C-C3FC-4A7B-BE3F-16E694B3B0B3@gmail.com

Nicholas Krause <xerofoify <at> gmail.com> writes:

> 
> I have listened to peoples feedback.  Am I still missing something 
> as I now do
> 1. Build test all patches
> 2. Reading the code properly
> 3.Testing my patches 
> 4.Listening to feedback 
> Nick 
> 
[trim]

Insert this:

X. Do My Own Research First, THEN ask questions

preferably at X = 0, 2, 4, 6, 8 of the above list.

Read a few netiquette/'how to write questions smart' manuals
to learn how to let people /know/ you did your research.

If your school work gets in the way though,
it probably means it's much more important and you
should not miss it.

Cheers,

CHSMBIDWT/MSPANC.

el es

  reply	other threads:[~2015-03-23 13:51 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
2015-03-15 17:16             ` Nicholas Krause
2015-03-23 13:51               ` el_es [this message]
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=loom.20150323T144133-770@post.gmane.org \
    --to=el.es.cr@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).