unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 69646@debbugs.gnu.org
Subject: bug#69646: [PATCH] Have insert 'submit-emacs-patch' maintainers into X-Debbugs-Cc
Date: Fri, 08 Mar 2024 12:41:27 -0500	[thread overview]
Message-ID: <yp1r0gkwri0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <871q8kel1w.fsf@posteo.net> (Philip Kaludercic's message of "Fri,  08 Mar 2024 16:38:03 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

> Andrea Corallo <acorallo@gnu.org> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>>> Tags: patch
>>>
>>>
>>> Here's a suggestion, to have the submit-emacs-patch command
>>> automatically ping maintainers, in case they are not following the bug
>>> tracker.  Basically it goes through all the files and extracts the
>>> information from the Maintainer: header.
>>>
>>> One non-technical issue here is that the maintainer information might
>>> not be up to date.  I've run a quick scan to see who is mentioned how
>>> frequently.  It might be necessary to clean up this list or to check who
>>> is still around:
>>
>> Hi Philip,
>>
>> IIUC with this patch I'd be in Cc of all bugs? If that's the case I'm
>> not personally in favor of this, I score mails on bug-gnu-emacs also
>> based on me being in Cc or not.
>
> Why should that be?  I have tested the new command out with bug#69647,
> and you weren't added automatically.  In fact, a quick grep tells me you
> aren't listed as the maintainer in any file, so you wouldn't be affected
> by this.

Maybe your patch should parse also admin/MAINTAINERS and collect names
from there as well?

>> I think the bug is that maintainers should be subscribed to
>> bug-gnu-emacs (otherwise I'm not sure how they can actually maintain).
>
> The issue is that for someone like me, who maintains a few little things
> around Emacs, following all bugs and all discussions would be too much.
>
>> Isn't a long list of people in Cc technically just another mailing list?
>
> It shouldn't be a long list, just the people responsible for the
> specific files being modified.  My idea is to have something comparable
> to Linux's "get_maintainer.pl"[0], and a bit more streamlined (assuming
> people even use M-x submit-emacs-patch).

If we want to Cc maintainers who are impacted by a patch I'm in favor,
if we want to Cc all maintainers then I'm not.  I haven't read your
patch but from the initial description I thought was the first case,
I've now the impression is the second.  Apologies if there was some
miss-understanding on my side.

Thanks

  Andrea





  parent reply	other threads:[~2024-03-08 17:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 15:47 bug#69646: [PATCH] Have insert 'submit-emacs-patch' maintainers into X-Debbugs-Cc Philip Kaludercic
2024-03-08 16:04 ` Andrea Corallo
2024-03-08 16:38   ` Philip Kaludercic
2024-03-08 16:53     ` Eric Abrahamsen
2024-03-08 17:41     ` Andrea Corallo [this message]
2024-03-08 17:50       ` Philip Kaludercic
2024-03-08 22:06 ` Felician Nemeth
2024-03-09  8:23   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-09 16:33     ` Felician Nemeth
2024-03-09 16:40       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-09  9:00   ` Philip Kaludercic

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yp1r0gkwri0.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=69646@debbugs.gnu.org \
    --cc=philipk@posteo.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).