From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: gnus-bug
Date: Tue, 30 Apr 2019 14:40:31 +0100 [thread overview]
Message-ID: <87a7g78vcg.fsf@tcd.ie> (raw)
In-Reply-To: <8736lzabfj.fsf@gnu.org> (Tassilo Horn's message of "Tue, 30 Apr 2019 15:07:44 +0200")
Tassilo Horn <tsdh@gnu.org> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>
>> Not sure whether that was asked before. Gnus is now part of GNU emacs,
>> should I still use
>>
>> 1. gnus-bug
>> 2. Or report-emacs-bug?
>
> The end result is always the same, a report in debbugs. What's a bit
> different is the default text inserted into the message.
Specifically, gnus-bug assigns the bug to both packages gnus and emacs,
whereas report-emacs-bug assigns it only to the emacs package.
The former is more useful for bug search and triage purposes, but the
latter includes more information about Emacs' state, so I think TRT
would be to make gnus-bug exactly like report-emacs-bug, except that it
also assigns the bug to the gnus package.
Now that Gnus is distributed with Emacs, I also think the
X-Debbugs-Version should be set to the version of Emacs, not Gnus.
While we're on the topic, can someone please have a look at bug#35239?
I think it's a pretty straightforward change and would like to push it
soon.
https://debbugs.gnu.org/35239
Thanks,
--
Basil
next prev parent reply other threads:[~2019-04-30 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 10:14 gnus-bug Uwe Brauer
2019-04-30 13:07 ` gnus-bug Tassilo Horn
2019-04-30 13:40 ` Basil L. Contovounesios [this message]
2019-04-30 15:29 ` gnus-bug Eli Zaretskii
2019-04-30 16:49 ` gnus-bug Eric Abrahamsen
2019-06-26 11:33 ` gnus-bug Basil L. Contovounesios
2019-04-30 17:10 ` gnus-bug Stefan Monnier
2019-04-30 17:46 ` gnus-bug Basil L. Contovounesios
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=87a7g78vcg.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--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 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).