From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-setup.el?
Date: 20 Apr 2000 20:34:00 +0200 [thread overview]
Message-ID: <m3zoqo7hbb.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vxkk8htcx83.fsf@mesquite.charcoal.com>
Karl Kleinpaste <karl@charcoal.com> writes:
> I was kinda thinking that we'd just get rid of it entirely, because I
> couldn't conceive at the time how it could still be useful, since it
> seemed to be actively damaging to a sensible environment. But I had a
> couple private replies saying that it's used, though the values
> contained there are of course being replaced by its users. (This
> makes me wonder what the value is from having it available at all.)
>
> I'll tweak the file a bit sometime soon.
If it has no value, we can remove it. If people are using it, it
would be better to update it. I've never used it myself...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2000-04-20 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 14:17 gnus-setup.el? Karl Kleinpaste
2000-04-11 20:42 ` gnus-setup.el? Michael Welsh Duggan
2000-04-20 0:13 ` gnus-setup.el? Lars Magne Ingebrigtsen
2000-04-20 2:39 ` gnus-setup.el? Karl Kleinpaste
2000-04-20 18:34 ` 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=m3zoqo7hbb.fsf@quimbies.gnus.org \
--to=larsi@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).