From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Garreau\, Alexandre" <galex-713@galex-713.eu>
Cc: ding@gnus.org
Subject: Re: `gnus-bug' bug? [
Date: Tue, 30 Oct 2018 14:33:40 -0700 [thread overview]
Message-ID: <8736sn9l1n.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87h8h4jal2.fsf_-_@portable.galex-713.eu> (Alexandre Garreau's message of "Tue, 30 Oct 2018 05:57:13 +0100")
"Garreau, Alexandre" <galex-713@galex-713.eu> writes:
> On 2018-10-29 at 10:17, Eric Abrahamsen wrote:
>> This sort of very specific suggestion could have gone in a bug report to
>> begin with, yes, though it doesn't matter too much. Gnus bugs are
>> reported along with Emacs bugs. You can also use `gnus-bug' to do the
>> report, in which case the bug will also be reported in the "Gnus
>> package", and you can see them here:
>>
>> https://debbugs.gnu.org/cgi/pkgreport.cgi?package=gnus
>>
>> But tbh I don't know if that's the right thing to do, since Gnus isn't
>> its own package anymore. It used to be, but is no longer, hence the
>> confusion.
>
> I mistakenly thought it would tag everything “gnus” as “emacs” too, as
> all “gnus” bug here are also tagged “emacs”: how were most of those
> reported?
Hmm, when I run `gnus-bug', it automatically adds this header to the
outgoing message:
X-Debbugs-Package: emacs,gnus
Which correctly tags the bug report with both headers. It looks like
this was added in last year, if you're not using a recent Emacs, maybe
that's not happening?
> On 1995-02-24 at 12:40, ding wrote:
>> If you want to report a bug, please type `M-x gnus-bug'. This will
>> give me a precise overview of your Gnus and Emacs version numbers,
>> along with a look at all Gnus variables you have changed.
Where did you find this?! It might have behaved this way in 1995, but it
certainly doesn't now, and I don't know when the changed-Gnus-variables
thing was removed.
Anyway, the correct debbugs packages are set for me here...
next prev parent reply other threads:[~2018-10-30 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 19:23 message-simplify-subject too coupled with reply (and not extensible) Garreau, Alexandre
2018-10-29 2:16 ` Eric Abrahamsen
2018-10-29 10:49 ` Garreau, Alexandre
2018-10-29 17:17 ` Eric Abrahamsen
2018-10-30 2:47 ` Garreau, Alexandre
2018-10-30 4:57 ` `gnus-bug' bug? [Was: Re: message-simplify-subject too coupled with reply (and not extensible)] Garreau, Alexandre
2018-10-30 21:33 ` Eric Abrahamsen [this message]
2018-11-01 4:17 ` `gnus-bug' bug? Garreau, Alexandre
2018-10-30 12:28 ` Two successive patches about the same function [Was: Re: message-simplify-subject too coupled with reply (and not extensible)] Garreau, Alexandre
2018-10-30 21:35 ` Two successive patches about the same function [ Eric Abrahamsen
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=8736sn9l1n.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
--cc=galex-713@galex-713.eu \
/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 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 NNTP newsgroup(s).