From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Expiry bug in nnmh.el
Date: Mon, 23 Mar 2015 00:13:15 +0100 [thread overview]
Message-ID: <878ueomxro.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.2517.1427034965.31049.info-gnus-english@gnu.org>
asjo@koldfront.dk (Adam Sjøgren) writes:
> Report it as an Emacs bug (M-x report-emacs-bug)
> and/or write to the Gnus development mailing list
> (ding@gnus.org).
There is also `gnus-bug' which is a mail to:
submit AT&T debbugs DOS gnu DOS org
`report-emacs-bug' should be fool-proof if in doubt
what method to use. I would think `gnus-bug' picks up
more Gnus specific data though, so perhaps that should
be used for Gnus bugs. Yeah, that seems logical.
--
underground experts united
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2015-03-22 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 12:43 Ben Bacarisse
2015-03-22 14:35 ` Adam Sjøgren
2015-03-29 0:35 ` Ben Bacarisse
[not found] ` <mailman.2517.1427034965.31049.info-gnus-english@gnu.org>
2015-03-22 23:13 ` Emanuel Berg [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=878ueomxro.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=info-gnus-english@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.
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).