From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Tom spole¹
Date: 25 Oct 1998 23:51:49 +0100 [thread overview]
Message-ID: <m3g1ccp856.fsf@sparky.gnus.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 679 bytes --]
I've now gone through all the old gnus-bug reports and responded to
them all and stuff. (Yes, I slipped again, but only for 12 weeks this
time.) So if you have some outstanding bug report and haven't gotten
a reply, that means that I've lost it. Er. Not *lost* it (any more
than usual), but lost *it*. So send me a new bug report.
Oh, and the bug report doesn't really have to be outstanding.
Ordinary bug reports are also ok.
-----
¹) Studies have shown that this reference is something that's
understood only by 3% of Swedish people (and 0% of non-Swedish people)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Magne Ingebrigtsen
reply other threads:[~1998-10-25 22:51 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=m3g1ccp856.fsf@sparky.gnus.org \
--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).