From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: Weird number of messages on server
Date: Tue, 06 Feb 2007 11:35:58 -0500 [thread overview]
Message-ID: <g69wt2vw8ep.fsf@dhcp-65-162.kendall.corp.akamai.com> (raw)
In-Reply-To: <87bqk8uzfd.fsf@ixod.org>
On Mon, 05 Feb 2007 15:23:02 -0500 mark@ixod.org (Mark T.B. Carroll) wrote:
MTBC> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Sun, 04 Feb 2007 13:28:46 -0500 mark@ixod.org (Mark T.B. Carroll) wrote:
MTBC> (snip)
MTBC> I sometimes see something similar - see my report at
MTBC> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393546
>>
MTBC> I find that removing all mention of the afflicted groups from Gnus'
MTBC> files, then resubscribing, etc. fixes the problem when it happens.
>>
>> I hope that works. I've never seen this bug. If you can replicate it
>> reliably, turn on the NNTP log, and try to submit a bug You may need
>> to send us your newsrc.eld and other bits.
MTBC> Cool. FWIW there's an NNTP log snip in that bug (it doesn't seem to
MTBC> include the server's actual responses, just what was sent) and my
MTBC> .gnus.el was as in
MTBC> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355071
MTBC> It's not happening at the moment, but if it happens again I'll gather a
MTBC> copy of the newsrc.eld and let you guys know.
Great, thanks Mark. If you don't hear from a Gnus developer in a few
days, remind me and I'll follow up on the ding mailing list.
MTBC> The only really irritating bug right now is
MTBC> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379665
MTBC> (I have seven open bugs filed with Debian)
Unfortunately I don't use the Agent personally, and was not involved
at all in the code for it, so I can't suggest anything. As with the
other bug, let me know if you haven't heard about it from a Gnus
developer.
Generally Gnus bugs should be submitted with M-x gnus-bug instead of
through Debian for the fastest response. I am on the ding mailing
list, and I don't remember anything from the Debian people in years
(but I may have missed it). We do get reports from Emacs, though,
since Gnus is included in Emacs.
Ted
next prev parent reply other threads:[~2007-02-06 16:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 17:04 giglio robbo' d'acciaio
2007-01-26 18:58 ` Ted Zlatanov
2007-01-27 9:17 ` giglio robbo' d'acciaio
2007-01-27 14:01 ` giglio robbo' d'acciaio
2007-01-27 17:10 ` giglio robbo' d'acciaio
2007-01-29 17:11 ` Ted Zlatanov
2007-02-04 10:05 ` giglio robbo' d'acciaio
2007-02-04 18:28 ` Mark T.B. Carroll
2007-02-05 17:40 ` Ted Zlatanov
2007-02-05 20:23 ` Mark T.B. Carroll
2007-02-06 16:35 ` Ted Zlatanov [this message]
2007-02-05 20:28 ` giglio robbo' d'acciaio
2007-02-05 20:40 ` Mark T.B. Carroll
2007-02-06 16:40 ` Ted Zlatanov
2007-02-10 15:54 ` giglio robbo' d'acciaio
2007-02-10 19:58 ` Michael Widerkrantz
2007-02-12 19:02 ` Ted Zlatanov
2007-02-05 20:27 ` giglio robbo' d'acciaio
2007-02-05 20:41 ` Mark T.B. Carroll
2007-01-26 18:58 ` giglio robbo' d'acciaio
2007-02-09 15:09 ` Michael Widerkrantz
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=g69wt2vw8ep.fsf@dhcp-65-162.kendall.corp.akamai.com \
--to=tzz@lifelogs.com \
--cc=info-gnus-english@gnu.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).