From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] s/@filename/@path/ in MBox#store_message
Date: Sun, 10 Oct 2010 08:56:09 +0200 [thread overview]
Message-ID: <1286693669-sup-9131@dolk> (raw)
In-Reply-To: <a53ff2538f3de566eecc.1286662281@nagato.alloy-d.net>
Excerpts from Adam Lloyd's message of 2010-10-10 00:11:21 +0200:
> This fixes issues 79 and 89, related to crashes on sending mail.
I think your best bet is to close them yourself (if patches applied),
the issue tracker don't seem to be horribly well-maintained ;)
- gaute
next prev parent reply other threads:[~2010-10-10 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 22:11 Adam Lloyd
2010-10-10 6:56 ` Gaute Hope [this message]
2010-10-10 7:43 ` Rich Lane
-- strict thread matches above, loose matches on Subject: below --
2010-08-17 1:18 Adam Lloyd
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=1286693669-sup-9131@dolk \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.org \
/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