From: "Robert P. J. Day" <rpjday@mindspring.com>
To: debian developer <debiandev@gmail.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH - 1/1] Documentation/HOWTO
Date: Fri, 18 May 2007 12:01:41 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705181200440.18186@localhost.localdomain> (raw)
In-Reply-To: <f24d23310705180629x50c56ayfdcde357f0373fc4@mail.gmail.com>
On Fri, 18 May 2007, debian developer wrote:
...
> -Managing bug reports
> ---------------------
> -
> -One of the best ways to put into practice your hacking skills is by fixing
> -bugs reported by other people. Not only you will help to make the kernel
> -more stable, you'll learn to fix real world problems and you will improve
> -your skills, and other developers will be aware of your presence. Fixing
> bugs is one of the best ways to get merits among other developers, because
> not many people like wasting time fixing other people's bugs.
^^^^^^^ ^^^^
you might want to find a less demeaning term for debugging than
"wasting time." just a thought.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-05-18 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 13:29 debian developer
2007-05-18 14:01 ` Pekka Enberg
2007-05-18 16:01 ` Robert P. J. Day [this message]
2007-05-18 16:37 ` Bernd Eckenfels
2007-05-25 16:24 ` Scott Preece
2007-05-25 20:00 ` Bernd Eckenfels
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=Pine.LNX.4.64.0705181200440.18186@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=debiandev@gmail.com \
--cc=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®