From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 66620@debbugs.gnu.org
Subject: [bug#66620] [PATCH] doc: Document extra Emacs-Debbugs configurations.
Date: Thu, 19 Oct 2023 22:01:44 -0400 [thread overview]
Message-ID: <87v8b2m4qf.fsf@gmail.com> (raw)
In-Reply-To: <871qdr143j.fsf@gmx.de> (Michael Albinus's message of "Thu, 19 Oct 2023 09:08:48 +0200")
Hello,
Michael Albinus <michael.albinus@gmx.de> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
> Hi,
>
>> * doc/contributing.texi (Viewing Bugs within Emacs): Document
>> debbugs-gnu-default-packages, debbugs-gnu-default-severities.
>> (Debbugs User Interfaces): Likewise, and mention debbugs-gnu-guix-search.
>
> FTR, if wanted by the Guix project, we could also extend
> debbugs-gnu-guix.el. For example, loading this library could set
> debbugs-gnu-default-packages and debbugs-gnu-default-severities as
> proposed here.
Would that conflict with a user-set debbugs-gnu-default-packages or
debbugs-gnu-default-severities variables? I'm thinking of a mainly
Emacs developer sometimes also dabbling with Guix, which may want to
have their debbugs-gnu-default-packages set to "emacs" and the likes
even if also using debbugs-guix.el.
If it'd be used as a fall-back to user-specified versions, then that'd
be nice, I think!
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-20 2:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 0:34 [bug#66620] [PATCH] doc: Document extra Emacs-Debbugs configurations Maxim Cournoyer
2023-10-19 7:08 ` Michael Albinus
2023-10-19 10:29 ` Simon Tournier
2023-10-19 10:44 ` Michael Albinus
2023-10-20 2:01 ` Maxim Cournoyer [this message]
2023-10-20 8:39 ` Michael Albinus
2023-10-20 15:31 ` Maxim Cournoyer
2023-11-11 12:37 ` pelzflorian (Florian Pelz)
2023-12-30 14:45 ` pelzflorian (Florian Pelz)
2023-12-31 6:06 ` bug#66620: " Maxim Cournoyer
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=87v8b2m4qf.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=66620@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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/guix.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.