Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: kendall@clarkparsia.com (kendall at clarkparsia.com)
Subject: [sup-talk] [PATCH] Fix a bug about forwarding that trimmed out newlines.
Date: Fri, 4 Apr 2008 12:16:40 -0400 (EDT)	[thread overview]
Message-ID: <59971.192.168.1.71.1207325800.webmail@192.168.1.71> (raw)

On Friday, April 4, 2008 12:09pm, Nicolas Pouillard <nicolas.pouillard at gmail.com> said:

> This seems to happen when one don't touch the forwarded
> email. Indeed most of the sup's code tend to assume that
> messages body are reprensented using an array of string
> *without* a trailing \n, except some parts of the code.

I confirm this. It happens to me when I forward messages without editing them. It does not happen to messages that I edit (in any way).

Cheers,
Kendall



             reply	other threads:[~2008-04-04 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 16:16 kendall at clarkparsia.com [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-04 16:09 Nicolas Pouillard
2008-04-04 17:47 ` William Morgan
2008-04-05  9:26   ` Nicolas Pouillard
2008-04-21  8:02 ` Nicolas Pouillard
2008-04-23  1:44   ` William Morgan
2008-04-23  8:59     ` Nicolas Pouillard

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=59971.192.168.1.71.1207325800.webmail@192.168.1.71 \
    --to=kendall@clarkparsia.com \
    /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