From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Crash report: Draft message weirdness
Date: Mon, 19 May 2008 16:21:45 -0700 [thread overview]
Message-ID: <1211239250-sup-6528@south> (raw)
In-Reply-To: <1210201416-sup-3219@black-opal>
Reformatted excerpts from Kevin Riggle's message of 2008-05-07:
> I opened up a draft message I had saved on a thread of them, and when
> I was finished editing it, I tried to send it, and sup crashed.
Welcome ot the world of scary Ferret errors that seem to occur randomly.
If you sup-sync --changed sup://drafts, does that fix things?
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-05-19 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 23:11 Kevin Riggle
2008-05-07 23:13 ` Kevin Riggle
2008-05-19 23:21 ` William Morgan [this message]
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=1211239250-sup-6528@south \
--to=wmorgan-sup@masanjin.net \
/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