From: riel@surriel.com (Rik van Riel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Issues with Community
Date: Wed, 17 Sep 2014 09:13:38 -0400 [thread overview]
Message-ID: <54198902.8020203@surriel.com> (raw)
In-Reply-To: <5418C627.5010805@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/16/2014 07:22 PM, nick wrote:
> After numerous tries at good patches and still failing , I am
> listening to what you guys stated about my patches check it
> applies, grammar and build checks. I am still unable to get a good
> patch and would really appreciate it if someone walks me through
> one good patch as I will learn this will a tutor and the tutor can
> help be my router to the community
There are a lot of useful things to do in the Linux kernel community
besides writing patches.
One of the useful things you could do is simply run linux-next on your
system, and update whenever new linux-next code comes out. If it breaks
(which it sometimes does), you can write a bug report, and learn from
the resulting email thread what caused the problem.
Debugging is a much better way to learn development than developing
new patches from scratch "just because"...
- --
All rights reversed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUGYkCAAoJEM553pKExN6D6ikH/A2iC8wOm1Xa0rpna+i9cCyu
d3tZof+EbMLezsQjNDXHwJgm7bjsKHT55WT68snliugFueWfkX7c8S48wV2bNso6
iwObDGCt3iXnuNqWrZ4cjJg4Lk3vOWvs3D1FkCEBlhM8lafJZdaaQfXNVLkOAZyt
sg9rypTTeV8e1udp/O2UTNP9jwEasLqU3aGXj5AuTUGI77NiquUDn1fwlTwcregr
nkwv5iCoJuBifm8+GcHHReBzhWX/Ab4d8H+wNGsTHqhlDR3iNyaodMvlHLZcayry
gkZf3+VcZjR9XClBY5yLeNHmRcYeKFm80XeybF3Ih+zxluB5H2jEOKIp9/MbY88=
=S6vR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-09-17 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 23:22 Issues with Community nick
2014-09-17 10:00 ` Hugo Mills
2014-09-17 10:14 ` Jesus Bustos
2014-09-17 10:18 ` Anuz Pratap Singh Tomar
2014-09-17 10:36 ` Jake Campbell
2014-09-17 13:13 ` Rik van Riel [this message]
2014-09-17 17:02 ` Nick Krause
2014-09-17 18:59 ` Sudip Mukherjee
2014-09-17 19:51 ` Jason Conklin
2014-09-17 20:30 ` nick
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=54198902.8020203@surriel.com \
--to=riel@surriel.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.