All of lore.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jiri Kosina <jikos@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: FRV-setup: Clarification for "source code clean-up"?
Date: Fri, 21 Oct 2016 11:50:18 +0200	[thread overview]
Message-ID: <9944c3e8-f030-a500-682c-7a7c7a1f492b@users.sourceforge.net> (raw)
In-Reply-To: <20161021092730.GJ4418@mwanda>

> 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

WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jiri Kosina <jikos@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: FRV-setup: Clarification for "source code clean-up"?
Date: Fri, 21 Oct 2016 09:50:18 +0000	[thread overview]
Message-ID: <9944c3e8-f030-a500-682c-7a7c7a1f492b@users.sourceforge.net> (raw)
In-Reply-To: <20161021092730.GJ4418@mwanda>

> 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

  reply	other threads:[~2016-10-21  9:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21  5:03 [PATCH 0/6] FRV-setup: Fine-tuning for six function implementations SF Markus Elfring
2016-10-21  5:03 ` SF Markus Elfring
2016-10-21  5:05 ` [PATCH 1/6] FRV-setup: Use seq_puts() in show_cpuinfo() SF Markus Elfring
2016-10-21  5:05   ` SF Markus Elfring
2016-10-21  5:07 ` [PATCH 2/6] FRV-setup: Use seq_putc() " SF Markus Elfring
2016-10-21  5:07   ` SF Markus Elfring
2016-10-21  5:08 ` [PATCH 3/6] FRV-setup: Add some spaces for better code readability SF Markus Elfring
2016-10-21  5:08   ` SF Markus Elfring
2016-10-21  5:09 ` [PATCH 4/6] FRV-setup: Move "else" closer to a brace SF Markus Elfring
2016-10-21  5:09   ` SF Markus Elfring
2016-10-21  5:10 ` [PATCH 5/6] FRV-setup: Fix indentation in two lines SF Markus Elfring
2016-10-21  5:10   ` SF Markus Elfring
2016-10-21  7:24   ` Jiri Kosina
2016-10-21  7:24     ` Jiri Kosina
2016-10-21  7:51     ` Dan Carpenter
2016-10-21  7:51       ` Dan Carpenter
2016-10-21  9:11       ` FRV-setup: Clarification for "source code clean-up"? SF Markus Elfring
2016-10-21  9:11         ` SF Markus Elfring
2016-10-21  9:27         ` Dan Carpenter
2016-10-21  9:27           ` Dan Carpenter
2016-10-21  9:50           ` SF Markus Elfring [this message]
2016-10-21  9:50             ` SF Markus Elfring
2016-10-21 10:22             ` Dan Carpenter
2016-10-21 10:22               ` Dan Carpenter
2016-10-21 10:28               ` Geert Uytterhoeven
2016-10-21 10:28                 ` Geert Uytterhoeven
2016-10-21 11:03               ` Julia Lawall
2016-10-21 11:03                 ` Julia Lawall
2016-10-21 11:38                 ` Improving software around DMA API usage? SF Markus Elfring
2016-10-21 11:38                   ` SF Markus Elfring
2016-10-21  5:11 ` [PATCH 6/6] FRV-setup: Move statements for "case" to separate lines SF Markus Elfring
2016-10-21  5:11   ` SF Markus Elfring

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=9944c3e8-f030-a500-682c-7a7c7a1f492b@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=dan.carpenter@oracle.com \
    --cc=geert+renesas@glider.be \
    --cc=jikos@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.