From: Nick Andrew <nick@nick-andrew.net>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Cyrill Gorcunov <gorcunov@gmail.com>,
rdunlap@xenotime.net, tytso@mit.edu, hch@infradead.org,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
davem@davemloft.net, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments)
Date: Sun, 1 Jun 2008 02:23:13 +1000 [thread overview]
Message-ID: <20080531162312.GA5599@tull.net> (raw)
In-Reply-To: <9a8748490805211646s5ef93f8ey43ebbc7746fb1a3b@mail.gmail.com>
Suggestions ...
On Thu, May 22, 2008 at 01:46:28AM +0200, Jesper Juhl wrote:
> Ok, here's a first (very) rough draft of a KernelNewbieGuide document.
> It can certainly be expanded a lot and my grammar and spelling is far
> from perfect, but hey, it's a first rough draft :)
[...]
> - Go through the kernel Bugzilla (http://bugzilla.kernel.org/) and see
> if you can fix any of the many bugs filed in it. There's a metric
> butload of bugs filed in there that need attention.
"buttload"
> As far as tools go, all you really need are the tools compile the
> kernel (gcc, make etc) and a text editor to edit the source - vi,
> emacs, joe, almost anything will do fine.
"tools _to_ compile the kernel"
> Developing against anything older than the latest stable kernel is
> likely to be a waste of effort due to the rapid pace of
> development. Once you finish your patch against a several months (or
> even weeks) old kernel, your patch runs a great risk of being obsolete
> or impossible to apply (this greatly depends on the area you work on
> ofcours cince some areas change more rapidly than others, but do try
"of course, since"
> If your patch did not get applied and you recieved an ACK or some
"received"
> criticism about your patch, then your job is easy. If there's a very
> explicit rejection of the patch by the maintainer of the code with a
> good reason, then don't bother sending it again, it probably will
> never be applied. If the patch received improvement suggestions or
> other review comments, then you should create a new version of your
> patch that adresses the feedback you get and then re-submit (it's
> usually a good idea to list what stuff you've adressed when
> re-submitting).
"addressed".
I'd probably make a few grammatical changes too. When you're happy
with the content and your document is in the tree, I'll submit a
patch :-)
Nick.
--
PGP Key ID = 0x418487E7 http://www.nick-andrew.net/
PGP Key fingerprint = B3ED 6894 8E49 1770 C24A 67E3 6266 6EB9 4184 87E7
next prev parent reply other threads:[~2008-05-31 16:23 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 5:58 [PATCH] Standard indentation of arguments Jianjun Kong
2008-05-21 7:19 ` Jiri Slaby
2008-05-21 11:35 ` David Newall
2008-05-21 8:34 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Al Viro
2008-05-21 8:50 ` Andrew Morton
2008-05-21 9:19 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 9:41 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Al Viro
2008-05-21 17:44 ` Andrew Morton
2008-05-21 19:45 ` Theodore Tso
2008-05-21 20:38 ` Rene Herman
2008-05-21 20:50 ` Andrew Morton
2008-05-21 21:08 ` Rene Herman
2008-05-21 21:12 ` Andrew Morton
2008-05-21 21:32 ` Rene Herman
2008-05-22 19:40 ` Jaya Kumar
2008-05-21 10:32 ` Christoph Hellwig
2008-05-21 12:09 ` Theodore Tso
2008-05-21 17:46 ` Andrew Morton
2008-05-21 18:57 ` Cyrill Gorcunov
2008-05-21 19:31 ` Andrew Morton
2008-05-21 20:10 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 21:25 ` Willy Tarreau
2008-05-21 21:44 ` Stefan Richter
2008-05-21 21:56 ` Willy Tarreau
2008-05-21 21:08 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Valdis.Kletnieks
2008-05-21 23:01 ` Adrian Bunk
2008-05-21 23:17 ` Rene Herman
2008-05-21 23:55 ` Adrian Bunk
2008-05-22 0:10 ` Rene Herman
2008-05-22 14:31 ` Adrian Bunk
2008-05-21 23:35 ` Al Viro
2008-05-22 0:38 ` Adrian Bunk
2008-05-22 1:05 ` Alan Cox
2008-05-22 16:08 ` Stefan Richter
2008-05-21 19:33 ` Randy Dunlap
2008-05-21 19:45 ` Cyrill Gorcunov
2008-05-21 19:54 ` Andrew Morton
2008-05-21 20:06 ` Jesper Juhl
2008-05-21 20:27 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments), " Jonathan Corbet
2008-05-21 20:37 ` Jesper Juhl
2008-05-21 23:46 ` Jesper Juhl
2008-05-22 0:12 ` Adrian Bunk
2008-05-22 0:32 ` Jesper Juhl
2008-05-22 1:03 ` Alan Cox
2008-05-22 14:56 ` Pavel Machek
2008-05-22 15:29 ` Arjan van de Ven
2008-05-22 0:14 ` Al Viro
2008-05-22 0:34 ` Jesper Juhl
2008-05-22 1:07 ` Johannes Weiner
2008-05-22 4:51 ` Cyrill Gorcunov
2008-05-22 5:34 ` david
2008-05-31 16:23 ` Nick Andrew [this message]
2008-05-21 19:42 ` Johannes Weiner
2008-05-21 19:47 ` Cyrill Gorcunov
2008-05-21 19:49 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 22:03 ` Al Viro
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=20080531162312.GA5599@tull.net \
--to=nick@nick-andrew.net \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gorcunov@gmail.com \
--cc=hch@infradead.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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.