From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Bug reports
Date: 18 Feb 1996 12:09:36 +0100 [thread overview]
Message-ID: <w8sag2gritr.fsf@eistla.ifi.uio.no> (raw)
The number of bug reports has been tapering off lately. I just can't
believe that there's not oodles and oodles of bugs left in September,
so try to do more odd stuff to provoke Gnus to bug out on you. Take a
peek through the manual (the September 0.39 one, after it's been
released (hopefully tomorrow)) and see whether you find any new
functions you haven't used before, and use them, and send me bug
reports when they don't work. :-)
There are still quite a few non-processed bug reports from the last
month, though. I'm slowly whittling away on that list of "hmmm, how
odd" bugs. Feel free to send me new bug reports on the same subjects,
though. That might help.
--
"Yes. The journey through the human heart
would have to wait until some other time."
reply other threads:[~1996-02-18 11:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=w8sag2gritr.fsf@eistla.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).