[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9944c3e8-f030-a500-682c-7a7c7a1f492b@users.sourceforge.net>
Date: Fri, 21 Oct 2016 11:50:18 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Jiri Kosina <jikos@...nel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: FRV-setup: Clarification for "source code clean-up"?
> How are you going to fix bugs if you only send clean ups?
I would prefer an other wording than "only" in your question.
I imagine that probabilities and views will matter more for the handling
of a software error spectrum.
>> How do you think about to discuss corresponding software development
>> statistics in more detail?
>
> I think normal developers should fix 10 bugs or add a few features for
> every regression they introduce.
Are you looking for compensation possibilities?
> I introduced a regression just last week, so that's a normal part of life,
Thanks that you could also admit a programming mistake.
> but I was at least *trying* to fix a bug when I did it.
I am also trying to improve various software.
* We have got just different development opinions about the relevance
of some changes. Can such a disagreement be a useful source for
interesting ideas?
* We are used to inform further contributors about results from static
source code analysis.
These tools can find a bunch of open issues because of the automatic
application of special search patterns. The importance of such findings
will vary as usual.
Regards,
Markus
Powered by blists - more mailing lists