[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56003C79.40908@ahsoftware.de>
Date: Mon, 21 Sep 2015 19:20:57 +0200
From: Alexander Holler <holler@...oftware.de>
To: Austin S Hemmelgarn <ahferroin7@...il.com>,
Theodore Ts'o <tytso@....edu>,
Greg KH <gregkh@...uxfoundation.org>,
Josh Boyer <jwboyer@...oraproject.org>,
Eric Curtin <ericcurtin17@...il.com>,
Steve Calfee <stevecalfee@...il.com>,
Valentina Manea <valentina.manea.m@...il.com>,
Shuah Khan <shuah.kh@...sung.com>,
USB list <linux-usb@...r.kernel.org>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: First kernel patch (optimization)
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists