From: Bernd Eckenfels <be-mail2007@lina.inka.de>
To: Scott Preece <sepreece@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH - 1/1] Documentation/HOWTO
Date: Fri, 25 May 2007 22:00:05 +0200 [thread overview]
Message-ID: <20070525200005.GA2980@lina.inka.de> (raw)
In-Reply-To: <7b69d1470705250924x7ab2441bicee5d8cda7ff0d52@mail.gmail.com>
On Fri, May 25, 2007 at 11:24:46AM -0500, Scott Preece wrote:
> However, it might be phrased more diplomatically in this context, like
> "because you are sacrificing time that could be spent adding features,
> to fix somebody else's mistakes".
Not all Bugs are mistakes of the coder. I still think it is not correct to
blame developers. And it is also not a good idea to treat helping hands as
second class only because they improve instead of create things.
Linux Kernel is developed in a collaborative evolutionary process. The
documentation change is completely wrong worded.
(However the idea to ask ppl to look for small clear tasks, especially if
not everybody has the option to work on it (hardware) is good) - and very
rewarding.
Gruss
Bernd
next prev parent reply other threads:[~2007-05-25 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 13:29 [PATCH - 1/1] Documentation/HOWTO debian developer
2007-05-18 14:01 ` Pekka Enberg
2007-05-18 16:01 ` Robert P. J. Day
2007-05-18 16:37 ` Bernd Eckenfels
2007-05-25 16:24 ` Scott Preece
2007-05-25 20:00 ` Bernd Eckenfels [this message]
2007-05-18 17:26 ` Valdis.Kletnieks
2007-05-24 9:45 ` Qi Yong
2007-05-24 11:56 ` Diego Calleja
2007-05-24 15:49 ` Linus Torvalds
2007-05-24 16:28 ` debian developer
2007-05-25 7:13 ` Qi Yong
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=20070525200005.GA2980@lina.inka.de \
--to=be-mail2007@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sepreece@gmail.com \
/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.