From: Nevin Kapur <nkapur@cs.caltech.edu>
Subject: Re: [PATCH] Quieter gnus-registry
Date: Sat, 17 Jan 2004 15:40:57 -0800 [thread overview]
Message-ID: <m2ptdi87p2.fsf@nkpbook-invalid.cs.caltech.edu> (raw)
In-Reply-To: <plop87d69i4737.fsf@gnu-rox.org>
Xavier Maillard <zedek@gnu-rox.org> writes:
> I am personally against this patch since using gnus-verbose to
> something low can make gnus-registry be quiet.
I am happy with gnus normal verbosity. I would like to control
gnus-registry's verbosity.
> Normally you need to put gnus-verbose to something high to see "debug"
> informations so this patch seems useless to me.
I don't follow. With gnus-verbose set to the default, one shouldn't
see messages that don't convey any information at all.
("gnus-registry-split-fancy traced nil to nil.")
I think a variable to control is overkill. The developers should
decide if a message such as above has any value. If so, keep the
current behavior; if not, apply the patch.
-Nevin
next prev parent reply other threads:[~2004-01-17 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 18:04 Nevin Kapur
2004-01-17 21:07 ` Xavier Maillard
2004-01-17 23:40 ` Nevin Kapur [this message]
2004-01-18 9:26 ` Xavier Maillard
2004-01-21 0:11 ` Ted Zlatanov
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=m2ptdi87p2.fsf@nkpbook-invalid.cs.caltech.edu \
--to=nkapur@cs.caltech.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).