mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, debian developer <debiandev@gmail.com>
Subject: [PATCH] Fix duplicated entry in Documentation/HOWTO
Date: Sun, 20 May 2007 01:15:43 -0700	[thread overview]
Message-ID: <7v1whbsyfk.fsf_-_@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070518131749.GA4833@kroah.com> (Greg KH's message of "Fri, 18 May 2007 06:17:49 -0700")

Commit 3f271008 introduced this section to Linus tree, but a
later commit 722385f7 accepted almost the identical patch via
Greg's tree, both from the same author.

This kills the duplicated one.

Signed-off-by: Junio C Hamano <junkio@cox.net>
---
 Documentation/HOWTO |   20 --------------------
 1 files changed, 0 insertions(+), 20 deletions(-)

diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index 48123db..ced9207 100644
--- a/Documentation/HOWTO
+++ b/Documentation/HOWTO
@@ -396,26 +396,6 @@ bugme-janitor mailing list (every change in the bugzilla is mailed here)
 
 
 
-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.
-
-To work in the already reported bug reports, go to http://bugzilla.kernel.org.
-If you want to be advised of the future bug reports, you can subscribe to the
-bugme-new mailing list (only new bug reports are mailed here) or to the
-bugme-janitor mailing list (every change in the bugzilla is mailed here)
-
-	http://lists.osdl.org/mailman/listinfo/bugme-new
-	http://lists.osdl.org/mailman/listinfo/bugme-janitors
-
-
-
 Mailing lists
 -------------
 


      reply	other threads:[~2007-05-20  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f24d23310705180354l2995a89fhb513fe3e54221784@mail.gmail.com>
2007-05-18 10:56 ` Fwd: [BUG] HOWTO debian developer
     [not found]   ` <f24d23310705180409u1cbdcaa1o8302ea05830b75a@mail.gmail.com>
2007-05-18 12:40     ` debian developer
2007-05-18 13:17 ` Greg KH
2007-05-20  8:15   ` Junio C Hamano [this message]

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=7v1whbsyfk.fsf_-_@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --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®