mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Jani Nikula <jani.nikula@intel.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Vlastimil Babka <vbabka@suse.cz>
Subject: [PATCH] MAINTAINERS: remove duplicite bug filling description
Date: Mon, 19 Dec 2016 09:51:58 +0100	[thread overview]
Message-ID: <20161219085158.12114-1-vbabka@suse.cz> (raw)

I have noticed that two different descriptions for B: entries in MAINTAINERS
were merged: commit 686564434e88 ("MAINTAINERS: Add bug tracking system
location entry type") and 2de2bd95f456 ("MAINTAINERS: add "B:" for URI where
to file bugs").

This patch keeps the description from 2de2bd95f456. There has been a
discussion [1] about whether this more detailed description is useful and what
it exactly implies. I find it more useful and general, and the author of
686564434e88 agreed in the end that either is fine.

[1] https://lkml.org/lkml/2016/12/8/71

Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index f6eb97b35e0f..86398d275260 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -81,7 +81,6 @@ trivial patch so apply some common sense.
 	Q: Patchwork web based patch tracking system site
 	T: SCM tree type and location.
 	   Type is one of: git, hg, quilt, stgit, topgit
-	B: Bug tracking system location.
 	S: Status, one of the following:
 	   Supported:	Someone is actually paid to look after this.
 	   Maintained:	Someone actually looks after it.
-- 
2.11.0

                 reply	other threads:[~2016-12-19  8:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20161219085158.12114-1-vbabka@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.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 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®