lkml.org 
[lkml]   [2015]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: First kernel patch (optimization)
From
Date
Am 21.09.2015 um 17:47 schrieb Austin S Hemmelgarn:

> The problem I see with this argument is:
> 1. There's a lot of code in the kernel that wouldn't be merged today in
> the state it's in, this creates a false sense of what quality is
> expected for new code (BTRFS in particular comes to mind here).

Just to say it a last time, THE CODE I'VE POSTED WAS NEVER MEANT FOR
MERGING in that state. Regardless how many people will still come by and
repeat that it was ugly, bad and broken to just use that as an
additional argument against me.

I've absolutely no idea how you all start to test an idea and
demonstrate it others, but I don't waste time on such tasks with looking
for style, (premature) optimization or even races.

I know how write production ready code, doing such since a long time and
I know how much time that costs, and I know that only fools (or students
which have to show that they can write good code) spend this time for
code which might end up in the waste bin anyway.

Alexander Holler


\
 
 \ /
  Last update: 2015-09-21 19:41    [W:0.103 / U:0.340 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site