[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e2c26bc-d765-6225-af72-157832ab8785@gmail.com>
Date: Fri, 7 Oct 2016 07:52:22 -0400
From: "Austin S. Hemmelgarn" <ahferroin7@...il.com>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
Richard Weinberger <richard@....at>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
Guoqing Jiang <gqjiang@...e.com>, Jens Axboe <axboe@...com>,
Mike Christie <mchristi@...hat.com>,
Neil Brown <neilb@...e.com>, Shaohua Li <shli@...nel.org>,
Tomasz Majchrzak <tomasz.majchrzak@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
Julia Lawall <julia.lawall@...6.fr>
Subject: Re: md/raid1: Improve another size determination in setup_conf()
On 2016-10-07 06:50, SF Markus Elfring wrote:
>> Linux has tons of issues, fixes for real problems are very welcome.
>
> Is a spectrum of software improvements to reconsider there?
>
>
>> But coding style bike shedding is just a waste of time.
>
> Why do various software developers bother about coding style specifications
> at all then?
Coding style is important, but patches that just fix coding style are a
bad thing because they break things like `git blame` and run the risk of
introducing new bugs without any net benefit to end users. This goes
double for code you don't actually work on regularly or don't completely
understand.
Powered by blists - more mailing lists