From: igor.brkic@fer.hr (Igor Brkic)
Subject: [sup-talk] Introduction, thanks, and a small patch
Date: Sat, 15 Aug 2009 12:18:33 +0200 [thread overview]
Message-ID: <1250331013-sup-3083@xps> (raw)
In-Reply-To: <20090815041446.GA1249@yoom.home.cworth.org>
Excerpts from Carl Worth's message of Sub Kol 15 06:14:46 +0200 2009:
> PS. I'm sending this message from mutt since sup crashed when I tried
> to send the message (see exception output below). I think this is one
Hi Carl!
I had same problem with sup. Sup actually manages to send message before
crashing and then it crashes when indexing sent messages.
Solution that worked for me is to comment out line "Time.parse time, 0"
in mbox.rb file. This is not good solution, more like a hack, but for
some reason it works for me. Try it out.
I tried to find out why this is happening, but I'm not so familiar with
sup internals (and not so good in ruby too) and didn't come to any conclusion.
Igor
next parent reply other threads:[~2009-08-15 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090815041446.GA1249@yoom.home.cworth.org>
2009-08-15 10:18 ` Igor Brkic [this message]
2009-08-15 14:35 ` Carl Worth
2009-08-16 21:22 ` William Morgan
2009-08-16 23:18 ` Igor Brkic
2009-08-15 11:03 ` Marc Weber
2009-08-15 14:41 ` Carl Worth
2009-08-16 21:38 ` 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=1250331013-sup-3083@xps \
--to=igor.brkic@fer.hr \
/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