From: lawrence mitchell <wence@gmx.li>
Subject: Upgrading to Oort? (was: UTF-8 support in gnus)
Date: Sat, 13 Apr 2002 18:50:51 +0100 [thread overview]
Message-ID: <oul1ydjh4hw.fsf@ID-97657.usr.dfncis.de> (raw)
In-Reply-To: <m3pu135y4q.fsf@ichimusai.org>
ichi@ichimusai.org wrote:
[...]
> Is Oort gnus compatible with my configuration files specifically
> .gnus/.emacs?
Shouldn't be any reason that it isn't.
> Is the upgrade easy?
Relatively so, see <news:oul4riln6li.fsf@ID-97657.usr.dfncis.de> for
one explanation of how to. It's best to install in a separate
directory, so that you don't overwrite your existing Gnus
installation.
> Are there ready rpm's for Red Hat 7.2 available?
Not sure, but probably not.
> Are there any other issues I should be aware of before I might
> attempt it?
> What is the main difference between Oort gnus and the "normal" gnus?
Oort is technically alpha software, i.e. it may, potentially be
unstable. It may do nasty things to your mail. In practice, I
haven't had any problems at all, but YMMV.
--
lawrence mitchell <wence@gmx.li>
next parent reply other threads:[~2002-04-13 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m37knbg4k2.fsf@ichimusai.org>
[not found] ` <m3lmbrlpll.fsf@barnowl.demon.co.uk>
[not found] ` <m3pu135y4q.fsf@ichimusai.org>
2002-04-13 17:50 ` lawrence mitchell [this message]
[not found] ` <87wuvba3my.fsf@enberg.org>
[not found] ` <m3hemf43ec.fsf@ichimusai.org>
2002-04-14 3:13 ` UTF-8 support in gnus Henrik Enberg
2002-04-14 12:39 ` Kai Großjohann
2002-04-13 19:23 ` Kai Großjohann
[not found] ` <87g01zh8fs.fsf@bretagne.rail.eu.org>
2002-04-13 19:24 ` Kai Großjohann
[not found] ` <v9u1qdji2l.fsf@marauder.physik.uni-ulm.de>
[not found] ` <m3hemcvhnz.fsf@ichimusai.org>
[not found] ` <v93cxwabih.fsf_-_@marauder.physik.uni-ulm.de>
2002-04-16 6:49 ` cc-decode-utf8 (was: UTF-8 support in gnus) Christoph Conrad
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=oul1ydjh4hw.fsf@ID-97657.usr.dfncis.de \
--to=wence@gmx.li \
/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).