From: Christoph Conrad <christoph.conrad@gmx.de>
Cc: Gnus Beta Testers <ding@gnus.org>
Subject: Re: [RFC] nnmbox and first-time users
Date: Wed, 21 Nov 2001 23:08:25 +0100 [thread overview]
Message-ID: <m37ksjydye.fsf@ID-24456.user.dfncis.de> (raw)
In-Reply-To: <vafd72c86ug.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 21 Nov 2001 16:46:31 +0100")
> In fact I think that slowly the time might have come to change a
> lot of important variables in an incompatible manner. That will
> at least show the users that something is wrong, and so they can
> correct it.
If that is done this change should be documented in a VERY explicit
manner accompanied by a good "transition description".
next prev parent reply other threads:[~2001-11-21 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 15:15 Didier Verna
2001-11-21 15:46 ` Kai Großjohann
2001-11-21 17:40 ` Paul Jarc
2001-11-22 9:16 ` Kai Großjohann
2001-11-21 22:08 ` Christoph Conrad [this message]
2001-11-22 9:17 ` Kai Großjohann
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=m37ksjydye.fsf@ID-24456.user.dfncis.de \
--to=christoph.conrad@gmx.de \
--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).