Gnus development mailing list
 help / color / mirror / Atom feed
From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Michael Albinus <michael.albinus@gmx.de>
Cc: help-debbugs@gnu.org, Noam Postavsky <npostavs@gmail.com>, ding@gnus.org
Subject: Re: `gnus-bug' bug?
Date: Thu, 01 Nov 2018 05:17:38 +0100	[thread overview]
Message-ID: <87k1lxo2hp.fsf_-_@portable.galex-713.eu> (raw)
In-Reply-To: <8736sn9l1n.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 30 Oct 2018 14:33:40 -0700")

On 2018-10-31 at 20:49, Michael Albinus wrote:
> Noam Postavsky <npostavs@gmail.com> writes:
>>> So first, dear GNU debbugs people, would it be currently possible
>>> for “gnus” bugs to be automatically tagged “emacs”?  would it be
>>> hard to hack debbugs to do so (so to deal with such “subpackages”)?
>>> Or should “gnus” package be removed?
>>
>> I think the "gnus" package should be removed. It was discussed a bit
>> on Bug#20670 (not otherwise related):
>>
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20670#17
>
> I'm not sure. "gnus" is used as second package beside "emacs", so it is
> simple to filter for gnus bugs in debbugs. A gnus bug report, at least
> when calling "M-x gnus-bug", adds the header "X-Debbugs-Package: emacs,gnus",
> which sounds OK to me. This was changed by Lars on Feb 7 2017, so I
> guess all Emacs versions since 26.1 behave so.

So they’re not obsolete anymore? Cool, for the same reasons mentioned
here!

I’m directing this mail to Lars to ask him how’s that evolving in the
end, if `gnus-bug' is going to be kept and possibly improved (again?)
upon.

I mean, `org-mode' is not even (yet?) a debbugs package per se, and yet
have (too) its own mailing-list (though it’s GNU) and its own
`org-submit-bug-report', too… except `org-submit-bug-report' submit also
changed variables list, for debugging purpose, while `gnus-bug'… but
then, for it to be perfect maybe once more:

On 2018/10/30 at 14h33, Eric Abrahamsen wrote:
> "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,

So everybody agrees as I heard this twice.

> if you're not using a recent Emacs, maybe that's not happening?

Yes.

>> 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.

So why doesn’t it do that anymore?  This is the only one detail that
makes `gnus-bug' looks as not totally superior and more specific than
`report-emacs-bug'.



  reply	other threads:[~2018-11-01  4:17 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         ` `gnus-bug' bug? [ Eric Abrahamsen
2018-11-01  4:17           ` Garreau, Alexandre [this message]
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=87k1lxo2hp.fsf_-_@portable.galex-713.eu \
    --to=galex-713@galex-713.eu \
    --cc=ding@gnus.org \
    --cc=help-debbugs@gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael.albinus@gmx.de \
    --cc=npostavs@gmail.com \
    /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).