From: daniel@electricrain.com (Dan Sully)
Subject: [sup-talk] sup errors with 0 messages in a folder
Date: Tue, 24 Jul 2007 11:14:17 -0700 [thread overview]
Message-ID: <20070724181417.GB20393@electricrain.com> (raw)
In-Reply-To: <1185299474-sup-18@south>
* William Morgan shaped the electrons to say...
>I don't have a good maildir testing setup any more. Can you try this
>quick fix? (Going through this code again reminds me how I need to
>rework it all...)
Yep - works much better than my hack did.
Thanks
-D
--
<dsully> please describe web 2.0 to me in 2 sentences or less.
<jwb> you make all the content. they keep all the revenue.
next prev parent reply other threads:[~2007-07-24 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 21:03 Dan Sully
2007-07-24 17:52 ` William Morgan
2007-07-24 18:14 ` Dan Sully [this message]
2007-07-24 18:26 ` Dan Sully
2007-07-24 22:14 ` William Morgan
2007-07-24 22:22 ` Dan Sully
2007-07-25 0:00 ` William Morgan
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=20070724181417.GB20393@electricrain.com \
--to=daniel@electricrain.com \
/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