From: "Bjørn Mork" <bmork@dod.no>
Subject: Server variables in ~/News/agent/lib/servers
Date: Thu, 06 Jun 2002 12:49:02 +0200 [thread overview]
Message-ID: <hvk7pchech.fsf@rasputin.ws.nextra.no> (raw)
Short question: Why?
Having them there means that agent forgets the server every time you
change its select-method by adding, removing or changing a variable.
I can't really see any reason why that's necessary, but maybe I'm
missing something? Why not use a reference to the select-method like
its done in ~/newsrc.eld?
Bjørn
--
How can you say that "Head-for-the-mountains" Bush was bad?
next reply other threads:[~2002-06-06 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 10:49 Bjørn Mork [this message]
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
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=hvk7pchech.fsf@rasputin.ws.nextra.no \
--to=bmork@dod.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).