mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@intel.com>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: jani.nikula@intel.com, Joe Perches <joe@perches.com>
Subject: Re: [PATCH 1/2] get_maintainer: add --bug option to print bug reporting info
Date: Mon, 26 Aug 2024 16:10:29 -0600	[thread overview]
Message-ID: <87h6b75416.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240815113450.3397499-1-jani.nikula@intel.com>

Jani Nikula <jani.nikula@intel.com> writes:

> For example Documentation/adming-guide/bug-hunting.rst suggest using
> get_maintainer.pl to get a list of maintainers and mailing lists to
> report bugs to, while a number of subsystems and drivers explicitly use
> the "B:" MAINTAINERS entry to direct bug reports at issue trackers
> instead of mailing lists and people.
>
> Add the --bug option to get_maintainer.pl to print the bug reporting
> URIs, if any.
>
> Cc: Joe Perches <joe@perches.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  scripts/get_maintainer.pl | 17 +++++++++++++++--
>  1 file changed, 15 insertions(+), 2 deletions(-)

I've applied both patches, thanks.

jon

      parent reply	other threads:[~2024-08-26 22:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 11:34 Jani Nikula
2024-08-15 11:34 ` [PATCH 2/2] Documentation: admin-guide: direct people to bug trackers, if specified Jani Nikula
2024-08-17  3:54   ` Joe Perches
2024-08-28 14:04   ` Joe Perches
2024-08-17  3:54 ` [PATCH 1/2] get_maintainer: add --bug option to print bug reporting info Joe Perches
2024-08-26 22:10 ` Jonathan Corbet [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=87h6b75416.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=jani.nikula@intel.com \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.org \
    --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®