From: Mark Plaksin <happy@usg.edu>
Subject: Re: Patch: Allow nnrss to be verbose
Date: Sun, 20 Feb 2005 05:42:45 -0500 [thread overview]
Message-ID: <m37jl3wlzu.fsf@water.tss.usg.edu> (raw)
In-Reply-To: <yotlmzu0xdjh.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Thanks. It seems to be useful. Is there any reason we're
> unable to make nnrss always verbose? (isn't the nnrss-verbose
> variable needless?)
*I* always want it verbose. I figured somebody would want it to be silent
:)
next prev parent reply other threads:[~2005-02-20 10:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 18:23 Mark Plaksin
2005-02-20 0:47 ` Katsumi Yamaoka
2005-02-20 10:42 ` Mark Plaksin [this message]
2005-02-20 11:43 ` Katsumi Yamaoka
2005-02-21 13:51 ` Arne Jørgensen
2005-02-21 14:34 ` Reiner Steib
2005-02-21 14:42 ` Arne Jørgensen
2005-02-21 14:54 ` Arne Jørgensen
2005-02-21 16:05 ` Reiner Steib
2005-02-21 22:52 ` Katsumi Yamaoka
2005-02-21 23:25 ` Katsumi Yamaoka
2005-03-02 16:48 ` Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch (was: Patch: Allow nnrss to be verbose) Reiner Steib
2005-04-05 0:43 ` Fixes for nnrss.el (and rfc2047.el) in the v5-10 branch Katsumi Yamaoka
2005-04-06 8:37 ` Katsumi Yamaoka
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=m37jl3wlzu.fsf@water.tss.usg.edu \
--to=happy@usg.edu \
/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).