mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Qi Yong" <qiyong@fc-cn.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
	"debian developer" <debiandev@gmail.com>,
	greg@kroah.com, linux-kernel@vger.kernel.org, diegocg@gmail.com,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH - 1/1] Documentation/HOWTO
Date: Thu, 24 May 2007 17:45:04 +0800	[thread overview]
Message-ID: <2cd57c900705240245s5448257ape203deade7812121@mail.gmail.com> (raw)
In-Reply-To: <10867.1179509181@turing-police.cc.vt.edu>

On 19/05/07, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Fri, 18 May 2007 12:01:41 EDT, "Robert P. J. Day" said:
> > On Fri, 18 May 2007, debian developer wrote:
>
> > > -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.
>
> Wasn't his text, not his fault.  At least his patch is an improvement - now
> HOWTO only equates it with "wasting time" once, rather than twice. ;)

Hello,

This duplicated paragraph problem was introduced by the following two
commits. They are one patch actually.

bughunting patch adds bug; isn't it a vivid ironic example.

and also
> +not many people like wasting time fixing other people's bugs.

Torvalds, Care to revert one commit?

commit 722385f75efd82d9f480f0765a1e97a4d83cac0d
Author: Diego Calleja <diegocg@gmail.com>
Date:   Thu Sep 21 22:37:10 2006 +0200

    HOWTO: bug report addition

    I suspect that not many people is subscribed to the bugzilla mailing list,
    not surprising since the URLs doesn't seem to be in the tree :)

    After fixing my english, I wonder if the following patch could be applied...

    Signed-off-by: Diego Calleja <diegocg@gmail.com>
    Acked-by: Randy Dunlap <rdunlap@xenotime.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

commit 3f27100872b21e4cc70d07b96eeb3611b30bce63
Author: Diego Calleja <diegocg@gmail.com>
Date:   Sat Sep 30 23:27:49 2006 -0700

    [PATCH] HOWTO: mention bughunting

    Signed-off-by: Diego Calleja <diegocg@gmail.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>


-- 
Qi Yong

  reply	other threads:[~2007-05-24  9:45 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
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 [this message]
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=2cd57c900705240245s5448257ape203deade7812121@mail.gmail.com \
    --to=qiyong@fc-cn.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=debiandev@gmail.com \
    --cc=diegocg@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=torvalds@linux-foundation.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®