From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>, "Tassilo Horn" <tsdh@gnu.org>
Cc: 72735@debbugs.gnu.org
Subject: bug#72735: 31.0.50; [PATCH] Make more bug-reference variables customizeable
Date: Tue, 20 Aug 2024 22:04:51 +0300 [thread overview]
Message-ID: <86plq3uib0.fsf@gnu.org> (raw)
In-Reply-To: <87a5h7hz3d.fsf@> (bug-gnu-emacs@gnu.org)
> Date: Tue, 20 Aug 2024 20:40:38 +0300
> From: Björn Bidar via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
>
> I noticed that there are other variable such as
> bug-reference-setup-from-mail-alist that should be change similarly.
Which ones, specifically?
And let's get Tassilo (CC'ed) on board of this discussion.
> Would it make sense to group the changes to convert them to defcustom in
> one patch or is one patch per variable better?
I prefer a single patch, thanks.
next parent reply other threads:[~2024-08-20 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a5h7hz3d.fsf@>
2024-08-20 19:04 ` Eli Zaretskii [this message]
2024-08-20 19:49 ` bug#72735: 31.0.50; [PATCH] Make more bug-reference variables customizeable Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-21 5:20 ` Tassilo Horn
2024-08-21 13:51 ` Eli Zaretskii
[not found] <874j7fnr75.fsf@>
2024-08-20 17:40 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-20 17:40 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-20 18:39 ` Eli Zaretskii
2024-08-20 19:39 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <875xrvhtll.fsf@>
2024-08-21 13:27 ` Eli Zaretskii
2024-08-20 15:34 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86plq3uib0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72735@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=tsdh@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.