From: Chris Tessone <tessone@imsa.edu>
Cc: ding@gnus.org
Subject: Re: Incoming* files
Date: 27 Oct 1998 19:05:50 -600 [thread overview]
Message-ID: <x3g3e89xzpt.fsf@cappio.imsa.edu> (raw)
In-Reply-To: Justin Sheehy's message of "27 Oct 1998 19:58:03 -500"
>>>>> "Justin" == Justin Sheehy <justin@linus.mitre.org> writes:
Justin> Yes. The purpose of that setting, and its default to 't,
Justin> is that you are using an _alpha_ release of Gnus. Keeping
Justin> the Incoming* files gives one a bit of safety in case a
Justin> rogue Gnus release eats mail.
Exactly. Which is why I don't let Gnus delete incoming mail and do so
by cron job every two days or so instead. :-)
--
I know who you are... You're one of those TREKKIES, aren't you!
next prev parent reply other threads:[~1998-10-28 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-28 1:06 Maciej Matysiak
1998-10-28 0:19 ` Jeremy D. Zawodny
1998-10-28 0:46 ` Maciej Matysiak
1998-10-28 0:58 ` Justin Sheehy
1998-10-28 1:05 ` Chris Tessone [this message]
1998-10-28 1:43 ` Maciej Matysiak
1998-10-28 1:44 ` Jeremy D. Zawodny
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=x3g3e89xzpt.fsf@cappio.imsa.edu \
--to=tessone@imsa.edu \
--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).