From: taruti@taruti.net (Taru Karttunen)
Subject: [sup-talk] Sup crashing
Date: Mon, 17 Aug 2009 10:22:35 +0300 [thread overview]
Message-ID: <1250493725-sup-5683@oz.taruti.net> (raw)
In-Reply-To: 1250281208-sup-4199 <1250281208-sup-4199@masanjin.net>
Excerpts from William Morgan's message of Fri Aug 14 23:20:28 +0300 2009:
>
> Weird. Does sup-sync --optimize fix anything?
Made things work again. Thanks.
- Taru Karttunen
next prev parent reply other threads:[~2009-08-17 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 7:32 Taru Karttunen
2009-08-14 20:20 ` William Morgan
2009-08-17 7:22 ` Taru Karttunen [this message]
2009-08-17 14:01 ` William Morgan
2010-08-20 12:34 Mariano Mara
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=1250493725-sup-5683@oz.taruti.net \
--to=taruti@taruti.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