From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] preparing for 0.7
Date: Thu, 19 Mar 2009 13:41:06 -0700 [thread overview]
Message-ID: <a412e2a70903191341o744efb9bw3a02ebb1585a9b8b@mail.gmail.com> (raw)
In-Reply-To: <1237490703-sup-4095@entry>
On Thu, Mar 19, 2009 at 12:25 PM, William Morgan
<wmorgan-sup at masanjin.net> wrote:
> Hm, that would be bad. The right way to debug this is to wait for it to
> happen again (!) and examine the contents of the poll-mode and log-mode
> buffers, which should describe what Sup thinks it was doing at the time.
That's my plan. I did look at the two log buffers when I noticed
the problem, but by then it was too late. I'll keep an eye on it.
next prev parent reply other threads:[~2009-03-19 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 17:27 William Morgan
2009-03-17 18:29 ` Mark Alexander
2009-03-18 13:49 ` William Morgan
2009-03-18 15:39 ` Lee Hinman
2009-03-19 17:02 ` William Morgan
2009-03-18 21:11 ` Mark Alexander
2009-03-19 19:18 ` Mark Alexander
2009-03-19 19:25 ` William Morgan
2009-03-19 20:41 ` Mark Alexander [this message]
2009-04-15 17:29 ` [sup-talk] Lost Maildir Messages Iain
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=a412e2a70903191341o744efb9bw3a02ebb1585a9b8b@mail.gmail.com \
--to=marka@pobox.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