From: Chris Marusich <cmmarusich@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: How to view the bug reports
Date: Tue, 05 Jun 2018 21:20:35 -0700 [thread overview]
Message-ID: <87wovco8a4.fsf@gmail.com> (raw)
In-Reply-To: <87k1rdnstk.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 05 Jun 2018 08:42:15 -0700")
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
Hi Eric,
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> news://news.gnus.org/gnus.gnus-bug
>
> I think gnus.org is out of date -- the debbugs system is the canonical
> bug tracker. You can browse it with the debbugs package, in the repos,
> which provides a few interactive commands for entering the bug browser.
>
> There's also `gnus-read-ephemeral-bug-group' for one-offs.
>
> [...]
>
> Note that if you run the `gnus-bug' command, it goes to
> submit@debbugs.gnu.org (with the "gnus" package tag).
That helps a lot! Thank you (and everyone else) for clarifying it.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-06-06 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 7:38 Chris Marusich
2018-06-05 15:42 ` Eric Abrahamsen
2018-06-05 15:57 ` Robert Pluim
2018-06-06 4:20 ` Chris Marusich [this message]
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=87wovco8a4.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).