From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: Re: Totally incorrect splitting
Date: Fri, 13 Dec 2013 13:07:47 -0600 [thread overview]
Message-ID: <m28uvovabg.fsf@nwalsh.com> (raw)
In-Reply-To: <87d2l0q191.fsf@flea.lifelogs.com> (Ted Zlatanov's message of "Fri, 13 Dec 2013 09:22:34 -0500")
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Ted Zlatanov <tzz@lifelogs.com> writes:
> You can set `gnus-verbose' to 9 and endure the noise until you catch the
> problem. Sorry I don't have a better way.
Ugh. It's pretty random and not something I notice right away.
I found a message that was misfiled and re-delivered it, but it got
put in the right place the second time :-(
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | You look wise. Pray correct that
http://nwalsh.com/ | error.--Charles Lamb
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 186 bytes --]
next prev parent reply other threads:[~2013-12-13 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 16:30 Norman Walsh
2013-12-10 17:07 ` Steinar Bang
2013-12-10 18:02 ` Norman Walsh
2013-12-13 14:22 ` Ted Zlatanov
2013-12-13 19:07 ` Norman Walsh [this message]
2014-01-30 14:58 ` Norman Walsh
2014-02-01 10:06 ` 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=m28uvovabg.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=ding@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).