From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Feature Freeze/Red Gnus
Date: 30 Jan 1996 17:29:52 +0100 [thread overview]
Message-ID: <w8sn375wsqn.fsf@aegir.ifi.uio.no> (raw)
In-Reply-To: Steven L Baur's message of 27 Jan 1996 16:30:11 -0800
Steven L Baur <steve@miranova.com> writes:
> One thing that's always bothered me about the current format is what
> happens if your NNTP server changes its domain name
> (ie. clue.callamer.com becomes twizzler.callamer.com)?
>
> Can I just rename .gnusrc-clue.callamer.com* to
> .gnusrc-twizzler.callamer.com? Or better still, can I make a symbolic
> link so the two are one and the same?
Yes, I think doing either would be unproblematic. (But I think you
mean ".newsrc-*" and not ".gnusrc-*" :-)
> Would it be possible for you to make (and distribute) a developer's
> kit with something like this for testing?
Yes. But it's too much work. So, no. :-(
> Lars> The server-specific information being the article numbers and article
> Lars> marks, and the server-independent being, well, all the rest? Levels,
> Lars> scores, names, and group parameters?
>
> Exactly. Given how expiration times have gone way down, it is far
> less important in moving to a new server knowing what articles you've
> already seen, than having all the group setup information preprepared.
Yes. I'd hate to have to recreate all my to-address params, virtual
server definitions, etc, if I had to move. Perhaps there should be a
command for generating a "clean" .newsrc? Remove all the article
number stuff and just have the server-independent things remain? I've
added that to the Red Gnus todo list.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-01-30 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-26 19:09 Steven L Baur
1996-01-27 20:33 ` Lars Magne Ingebrigtsen
1996-01-28 0:30 ` Steven L Baur
1996-01-30 16:29 ` Lars Magne Ingebrigtsen [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=w8sn375wsqn.fsf@aegir.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).