All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Mention regression mailing list in reporting-bugs and MAINTAINERS
Date: Tue, 13 Apr 2021 15:14:08 -0600	[thread overview]
Message-ID: <874kg9sx9b.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1617967127.git.linux@leemhuis.info>

Thorsten Leemhuis <linux@leemhuis.info> writes:

> Hi! A mailing list for regressions was finally created as
> regressions@lists.linux.dev (we dropped the linux- prefix as the term is already
> in the domain name). Hence, add it to MAINTAINERS, as that where people will
> look it up. I was a bit unsure how to actually do that, see the note in the
> first patch of the series for details.
>
> The second patch makes reporting-issues.rst mention the new list, so people CC
> it.
>
> @Jonathan: this hopefully is the last round of patches for reporting-issues.rst
> for this cycle. Please let me known if you think the addition to the MAINTAINERS
> file should better go through a different maintainer.

Naw...we all stick our fingers into MAINTAINERS at will...:)  I've
applied both, thanks.

jon

      parent reply	other threads:[~2021-04-13 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 11:47 [PATCH v2 0/2] Mention regression mailing list in reporting-bugs and MAINTAINERS Thorsten Leemhuis
2021-04-09 11:47 ` [PATCH v2 1/2] MAINTAINERS: add regressions mailing list Thorsten Leemhuis
2021-04-09 13:08   ` Greg KH
2021-04-09 11:47 ` [PATCH v2 2/2] docs: reporting-issues: make people CC the regressions list Thorsten Leemhuis
2021-04-09 13:09   ` Greg KH
2021-04-13 21:14 ` 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=874kg9sx9b.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=rdunlap@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.