From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Cc: ding@gnus.org
Subject: Re: guide or howto on updating gnus?
Date: 24 Jun 1999 23:34:01 +0200 [thread overview]
Message-ID: <86iu8d8era.fsf@slowfox.cs.uni-dortmund.de> (raw)
In-Reply-To: Jack Twilley's message of "Thu, 24 Jun 1999 14:42:21 GMT"
Jack Twilley <jmt+usenet@nycap.rr.com> writes:
> I'm an active ?gnus user, keeping up on the bleeding edge as best I
> can, but I'm not always able to figure out exactly what the changes
> are from version to version.
Are the changelog entries not sufficient to figure this out? I just
read this mailing list and this tells me enough about what's going
on. At least I didn't have any problems with the nnmail ->
mail-source transition, for instance.
kai
--
Abort this operation? [OK] [Cancel]
next prev parent reply other threads:[~1999-06-24 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-24 14:42 Jack Twilley
1999-06-24 21:34 ` Kai.Grossjohann [this message]
1999-06-28 20:45 ` Wes Hardaker
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=86iu8d8era.fsf@slowfox.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).