From: "Paul D. Smith" <psmith@BayNetworks.com>
Subject: Re: [19.30.94] customize & GNUS broken
Date: Mon, 11 Mar 96 14:30:05 EST [thread overview]
Message-ID: <9603111930.AA06940@lemming.engeast> (raw)
In-Reply-To: <9603111836.AA06807@lemming.engeast>
Yikes!
Sorry for the deluge; the elisp tracebacks didn't look anywhere near
that big when I pasted them into my email buffer :-/.
-------------------------------------------------------------------------------
Paul D. Smith <psmith@baynetworks.com> Network Management Development
Senior Software Engineer Bay Networks, Inc.
-----------------------------------------------==<http://www.baynetworks.com/>-
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions--Bay Networks takes no responsibility for them.
prev parent reply other threads:[~1996-03-11 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-11 18:36 Paul D. Smith
1996-03-11 19:30 ` Paul D. Smith [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=9603111930.AA06940@lemming.engeast \
--to=psmith@baynetworks.com \
/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).