From: Don Saklad <dsaklad@nestle.ai.mit.edu>
Cc: kbk@shore.net, dsaklad@gnu.org
Subject: Re: How to develop an automatic set up experience for gnus email.
Date: 26 Nov 2002 01:18:42 -0500 [thread overview]
Message-ID: <y444ra44zwd.fsf@nestle.ai.mit.edu> (raw)
In-Reply-To: <m31y58532i.fsf@float.attbi.com>
...Great ! Thank you Kurt B. Kaiser !
If you don't or can't ask around
a. what system commands give one some information about one's system?...
b. what system files would contain information about one's system?...
information needed for composing the dotfile correctly and to the best
advantage for gnus email ?...
prev parent reply other threads:[~2002-11-26 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <y44wun1g3nb.fsf@nestle.ai.mit.edu>
2002-11-25 15:51 ` David Z Maze
[not found] ` <y444ra5l0vr.fsf@nestle.ai.mit.edu>
2002-11-26 5:10 ` Kurt B. Kaiser
2002-11-26 6:18 ` Don Saklad [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=y444ra44zwd.fsf@nestle.ai.mit.edu \
--to=dsaklad@nestle.ai.mit.edu \
--cc=dsaklad@gnu.org \
--cc=kbk@shore.net \
/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).