From: Laura Conrad <lconrad@gamesville.com>
Subject: Re: nnslashdot error
Date: 12 Nov 1999 09:50:22 -0500 [thread overview]
Message-ID: <kh71z9vrcgh.fsf@acme47.nineco.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "12 Nov 1999 14:28:41 +0100"
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> eldrik@logrus.com (Bruce Z. Lysik) writes:
>> Yep. Just checked it out again a second ago, and has the same
>> problem.
Lars> Are you sure? You've recompiled and restarted Emacs and
Lars> everything?
When we get a gnus update from cvs, do we always need to restart
emacs? I was hoping just restarting gnus would be enough.
--
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097 fax: (801) 365-6574
233 Broadway, Cambridge, MA 02139
next prev parent reply other threads:[~1999-11-12 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-12 1:15 Bruce Z. Lysik
1999-11-12 12:02 ` Lars Magne Ingebrigtsen
1999-11-12 13:11 ` Bruce Z. Lysik
1999-11-12 13:28 ` Lars Magne Ingebrigtsen
1999-11-12 13:40 ` Bruce Z. Lysik
1999-11-12 14:50 ` Laura Conrad [this message]
1999-11-12 15:12 ` Kai Großjohann
1999-11-12 15:25 ` Lars Magne Ingebrigtsen
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=kh71z9vrcgh.fsf@acme47.nineco.com \
--to=lconrad@gamesville.com \
--cc=lconrad@world.std.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).