From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Server variables in ~/News/agent/lib/servers
Date: Sun, 16 Jun 2002 22:56:45 +0200 [thread overview]
Message-ID: <ilufzzn2b8y.fsf@latte.josefsson.org> (raw)
In-Reply-To: <vaf660jgdch.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sun, 16 Jun 2002 22:47:42 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Bjørn Mork <bmork@dod.no> writes:
>
>> Which could have been better tested. Sorry. This one should be
>> correct.
>
> Committed.
How about auto-agentizing non-primary remote servers as well?
Perhaps we should wait longer to see if agentizing causes problems
though, I think we have one bug that may be caused by it now (the
daemon not working correctly). I have always agentized all remote
servers for a long time, and haven't seen anything weird.
Hm, my servers file looks like:
("nntp:quimby.gnus.org" "nntp:news.uslinuxtraining.com" "nnimap:yxa" nil)
where did the nil come from? Maybe the code should fall back to using
fully qualified servers if it cannot be "collapsed" into a smaller
one. I think the nil entry was a server that no longer exists, or a
server that still exists but used different parameters, or something
like that.
next prev parent reply other threads:[~2002-06-16 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 10:49 Bjørn Mork
2002-06-11 19:56 ` Simon Josefsson
2002-06-14 16:43 ` Bjørn Mork
2002-06-15 17:34 ` Kai Großjohann
2002-06-16 19:43 ` Bjørn Mork
2002-06-16 19:48 ` Bjørn Mork
2002-06-16 20:47 ` Kai Großjohann
2002-06-16 20:56 ` Simon Josefsson [this message]
2002-06-16 21:14 ` Bjørn Mork
2002-06-17 7:27 ` Simon Josefsson
2002-06-17 9:09 ` Bjørn Mork
2002-06-17 9:55 ` Simon Josefsson
2002-06-24 11:50 ` Steinar Bang
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=ilufzzn2b8y.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).