From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Jim Davidson <jdavidso@nospam.com>, ding@gnus.org
Subject: Re: Adding Babyl Group
Date: 31 Mar 2000 18:46:53 +0200 [thread overview]
Message-ID: <vafk8ijqe82.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich's message of "31 Mar 2000 16:13:43 +0200"
Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich <Peter.Weiss@germany.sun.com> writes:
> That's not very user-friendly. I guess I still haven't understand the
> gnus-way...
I have tried to help with my last message (of 2000-03-28). Feel free
to ask if that message wasn't helpful.
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2000-03-31 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-28 13:45 Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich
2000-03-28 15:42 ` Kai Großjohann
2000-03-28 19:29 ` Jim Davidson
2000-03-31 14:13 ` Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich
2000-03-31 16:46 ` Kai Großjohann [this message]
2000-03-31 19:52 ` Jim Davidson
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=vafk8ijqe82.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
--cc=jdavidso@nospam.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).