From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Incoming695xtd and other such files
Date: 12 Mar 2001 21:30:51 +0100 [thread overview]
Message-ID: <vafbsr6pw5g.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87lmqcngaa.fsf@harpo.homeip.net> (Samuel Padgett's message of "11 Mar 2001 16:31:57 -0500")
On 11 Mar 2001, Samuel Padgett wrote:
> Actually, I believe he's running Oort Gnus, in which case the
> variable should be nil. Perhaps it's best not to change it when
> running a development version?
00ps. Of course. Silly me.
Safety nets are a Good Thing for users of development versions.
Beware of Oorts eating your mail for lunch :-)
(Not that this ever happened to me.)
kai
--
Be indiscrete. Do it continuously.
prev parent reply other threads:[~2001-03-12 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2g0gka2dd.fsf@snail.nowhere.ch>
2001-03-11 13:49 ` Karl Kleinpaste
2001-03-11 15:14 ` Kai Großjohann
2001-03-11 18:00 ` Alex Schroeder
2001-03-11 18:21 ` Norbert Koch
2001-03-11 19:10 ` Kai Großjohann
2001-03-11 21:31 ` Samuel Padgett
2001-03-12 20:30 ` Kai Großjohann [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=vafbsr6pw5g.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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).