All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Krause <xerofoify@gmail.com>
To: Paul Bolle <pebolle@tiscali.nl>
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, 7 Jul 2014 16:10:04 -0400	[thread overview]
Message-ID: <CAPDOMVh=WghTAm-O8HvbEXb4Qrp03bHJuw_qp9gp2Jmiov38mg@mail.gmail.com> (raw)
In-Reply-To: <1404757366.2014.13.camel@x220>

I do known what they mean. It's good work for a long time
that isn't getting worked on therefore it seems good for
me to work on.
Cheers Nick

On Mon, Jul 7, 2014 at 2:22 PM, Paul Bolle <pebolle@tiscali.nl> wrote:
> 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
>

  reply	other threads:[~2014-07-07 20:10 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
2014-07-07 20:10       ` Nick Krause [this message]
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='CAPDOMVh=WghTAm-O8HvbEXb4Qrp03bHJuw_qp9gp2Jmiov38mg@mail.gmail.com' \
    --to=xerofoify@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=tytso@mit.edu \
    /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.