From: Paul Bolle <pebolle@tiscali.nl>
To: Nick Krause <xerofoify@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Arm Compiler - Part 1 of Compiling Tests
Date: Mon, 07 Jul 2014 20:22:46 +0200 [thread overview]
Message-ID: <1404757366.2014.13.camel@x220> (raw)
In-Reply-To: <CAPDOMVjEmVJJEd_LVpCkXC8qR7APTKeHNJQSQ5SFNuWj9BQuLA@mail.gmail.com>
On Mon, 2014-07-07 at 13:35 -0400, Nick Krause wrote:
> On the other hand there seems to be too many FIXMEs in the main
> kernel for one person to fix.
A quick grep for FIXMEs (also including the "XXX" pattern, which
basically means the same thing) triggers over 7000 hits. Even with a
(rather optimistic) one hour per FIXME that's over three years of work
(assuming a sane working hours/year metric).
Moreover, you appear to misunderstand the meaning of these FIXMEs. It's
not a marker for something trivial that somehow never got done. It might
actually mean all kind of things. In many cases it points at a hard, or
time consuming, etc., problem that no one has yet found a way, or the
time, to fix properly.
I would not advise someone new to the kernel to grep for FIXMEs to see
if they could contribute something. There are many things those people
could do, but those FIXMEs seem an awkward place to start.
Paul Bolle
next prev parent reply other threads:[~2014-07-07 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 5:22 Arm Compiler - Part 1 of Compiling Tests Nick Krause
2014-07-07 13:46 ` Theodore Ts'o
2014-07-07 17:35 ` Nick Krause
2014-07-07 18:22 ` Paul Bolle [this message]
2014-07-07 20:10 ` Nick Krause
2014-07-08 14:37 ` Jason Cooper
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=1404757366.2014.13.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xerofoify@gmail.com \
/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