From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: jmt+usenet@nycap.rr.com, ding@gnus.org
Subject: Re: guide or howto on updating gnus?
Date: 28 Jun 1999 13:45:38 -0700 [thread overview]
Message-ID: <sd4sjs3vgt.fsf@oakdale.ucdavis.edu> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "24 Jun 1999 23:34:01 +0200"
>>>>> On 24 Jun 1999 23:34:01 +0200, Kai.Grossjohann@CS.Uni-Dortmund.DE said:
>> 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.
Kai> Are the changelog entries not sufficient to figure this out?
They aren't really sufficient for people who aren't that familiar with
the architecture of gnus... And the descriptions are short.
Something like the NEWS file works better. But then, I'm sure the
argument would be "if you're aren't all that familiar, you probably
shouldn't be using pgnus".
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
prev parent reply other threads:[~1999-06-28 20:45 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
1999-06-28 20:45 ` Wes Hardaker [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=sd4sjs3vgt.fsf@oakdale.ucdavis.edu \
--to=wjhardaker@ucdavis.edu \
--cc=ding@gnus.org \
--cc=jmt+usenet@nycap.rr.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).