From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Fix message_to_chunks for the m.body == nil case.
Date: Sat, 26 Sep 2009 11:12:24 -0700 [thread overview]
Message-ID: <1253988663-sup-3838@masanjin.net> (raw)
In-Reply-To: <1253217341-sup-8631@yoom.home.cworth.org>
Reformatted excerpts from Carl Worth's message of 2009-09-17:
> The code was previously broken in calling EnclosedMessage.new with
> only 2 instead of 5 arguments.
Thanks, this has been applied.
> So I'm not 100% sure that this patch is correct, but it does allow
> sup-sync to proceed and the message appears in sup as well as could be
> expected, (the "extra" headers from the corrupted mime part appear in
> the body as one might expect here).
Yeah, I think that's the best we can hope for here.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-09-26 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 20:05 Carl Worth
2009-09-26 18:12 ` 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=1253988663-sup-3838@masanjin.net \
--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