From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: [PATCH] Quieter gnus-registry
Date: Sat, 17 Jan 2004 22:07:40 +0100 [thread overview]
Message-ID: <plop87d69i4737.fsf@gnu-rox.org> (raw)
In-Reply-To: <m23caea1ua.fsf@nkpbook-invalid.cs.caltech.edu> (Nevin Kapur's message of "Sat, 17 Jan 2004 10:04:29 -0800")
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
On 17 Jan 2004, Nevin Kapur uttered the following:
> I am proposing the following the patch for
> gnus-registry-split-fancy-with-parent. It suppresses messages in the
> minibuffer that don't convey any useful information.
I am personally against this patch since using gnus-verbose to
something low can make gnus-registry be quiet.
Normally you need to put gnus-verbose to something high to see "debug"
informations so this patch seems useless to me.
zeDek
--
"Emacs is a nice operating system, but I prefer UNIX." - Tom Christiansen
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-01-17 21:07 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 [this message]
2004-01-17 23:40 ` Nevin Kapur
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=plop87d69i4737.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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).