unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
	tsdh@gnu.org, emacs-devel@gnu.org
Subject: Re: gnus-bug
Date: Tue, 30 Apr 2019 09:49:52 -0700	[thread overview]
Message-ID: <87y33rfnf3.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <83ftpzse8r.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 30 Apr 2019 18:29:40 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> Date: Tue, 30 Apr 2019 14:40:31 +0100
>> Cc: emacs-devel@gnu.org
>> 
>> 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.
>
> I agree.

There was some talk a while ago about having `report-emacs-bug' prompt
for an optional sub-package (Gnus, Tramp, ERC, etc), and "do something
extra": add a tag, cc a maintainer, something like that. I still think
that's a good idea.



  reply	other threads:[~2019-04-30 16:49 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   ` gnus-bug Basil L. Contovounesios
2019-04-30 15:29     ` gnus-bug Eli Zaretskii
2019-04-30 16:49       ` Eric Abrahamsen [this message]
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=87y33rfnf3.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=contovob@tcd.ie \
    --cc=eliz@gnu.org \
    --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).