From: Robert Pluim <rpluim@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Our use of the "fixed" tag in debbugs
Date: Wed, 06 Oct 2021 09:44:07 +0200 [thread overview]
Message-ID: <87h7duwqbc.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkmkVEftqLBX7s9FY5SpsGn+j7RPz6oLbbmy8zv3xRwt=ug@mail.gmail.com> (Stefan Kangas's message of "Tue, 5 Oct 2021 15:44:08 -0400")
>>>>> On Tue, 5 Oct 2021 15:44:08 -0400, Stefan Kangas <stefan@marxist.se> said:
Stefan> Eli Zaretskii <eliz@gnu.org> writes:
>>> Currently, bugs are unfortunately just left open and untagged, which
>>> means that it can take a long time before someone goes back, tediously
>>> re-reads everything, and then closes it. Using this tag more often
>>> could save quite a bit of time, I hope.
>>
>> Tagging is tedious: you need to BCC the control address, you need to
>> type the line without making a mistake, etc. It's so much easier to
>> just close the bug.
Stefan> Indeed, it's a hassle. Perhaps it would help to have a command for this
Stefan> in `message-mode' much like `debbugs-gnu-make-control-message'? Or
Stefan> perhaps such a thing already exist?
I have a keybinding that does:
(re-search-forward "[Bb]ug#[0-9]" nil t)
(call-interactively #'gnus-read-ephemeral-bug-group)
(debbugs-gnu-summary-mode 1)
You can then do 'C' and 'E' to send/make control messages.
Hmm, it might even work to just do
(debbugs-gnu-summary-mode)
when reading the debbugs list, rather than having to create the
ephemeral group for a specific bug.
Robert
--
next prev parent reply other threads:[~2021-10-06 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 17:27 Our use of the "fixed" tag in debbugs Stefan Kangas
2021-10-05 17:52 ` Lars Ingebrigtsen
2021-10-05 17:56 ` Stefan Kangas
2021-10-05 17:57 ` Glenn Morris
2021-10-05 18:12 ` Basil L. Contovounesios
2021-10-05 19:08 ` Eli Zaretskii
2021-10-05 19:44 ` Stefan Kangas
2021-10-05 21:48 ` Stefan Monnier
2021-10-06 7:44 ` Robert Pluim [this message]
2021-10-08 11:21 ` Eli Zaretskii
2021-10-08 11:44 ` Basil L. Contovounesios
2021-10-08 15:41 ` Glenn Morris
2021-10-08 16:00 ` Basil L. Contovounesios
2021-10-08 17:16 ` Stefan Kangas
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=87h7duwqbc.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
/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).