From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Problems when upgrading newsrc from 5.9 to No Gnus
Date: Fri, 21 May 2004 11:02:14 -0500 [thread overview]
Message-ID: <uy8nlwyyh.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <v9wu36ugse.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> [ Taking this from gnu.emacs.help to ding... ]
>
> On Thu, May 20 2004, Miles Bader wrote:
>
> ,----[ <news:874qqb45ra.fsf@tc-1-100.kawasaki.gol.ne.jp> ]
> | I tried it out on a lark today (while setting up the gnus arch archive),
> | and it flaked out pretty badly, undefined variable errors, couldn't read
> | mail (got it from the server, but failed to store it in my mail
> | folders!). I even thought it trashed my .newsrc.eld file for a while --
> | it asked if I wanted to "upgrade" that file (irreversibly), recommended
> | I make a backup, and when I realized I'd better go back to 5.9, the
> | backup had been deleted! Luckily it turned out that the "upgrade" had
> | failed too... :-)
> `----
>
> ,----[ <news:87r7teu7k8.fsf@tc-1-100.kawasaki.gol.ne.jp> ]
> | BTW, about the .newsrc "upgrade" -- as I mentioned, it asked me, and
> | then failed to actually change anything.
> |
> | One thing that's funny about my Gnus setup is that I don't use a
> | .newsrc file -- I only have have a .newsrc.eld file. Should the
> | upgrade process cope with that situation?
> `----
>
> It should work, I think. But I'm not familiar with
> `gnus-convert-old-newsrc' and friends.
Thanks for the heads-up. I posted a response to Miles on
gnu.emacs.help to add some finality to that thread.
I'll see what I can do to make the conversion messages clearer.
Kevin
prev parent reply other threads:[~2004-05-21 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 12:05 Reiner Steib
2004-05-21 16:02 ` Kevin Greiner [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=uy8nlwyyh.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.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).