Your message dated Wed, 3 Jan 2007 16:33:58 +0100 (CET)
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #385251,
regarding pine: flowed text override with ^V doesn't work
to be marked as having been forwarded to the upstream software
author(s) Pine Bugs <[EMAIL PROTECTED]>.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Hello.
I received this report from the debian bug system.
[ Please keep the cc lines when replying ].
Thanks.
---------- Forwarded message ----------
From: Mike Isely <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Date: Tue, 29 Aug 2006 22:54:07 -0500
Subject: pine: flowed text override with ^V doesn't work
Package: pine
Version: 4.64-1
Severity: normal
Some background info: I hit this problem after 2 failed attempts to
submit some cypress_m8 driver patches to the linux-usb-devel mailing
list. The failure was due to the patches being subtlely
whitespace-mangled by pine, which was due to pine sending with flowed
text turned on. When flowed-text is not disabled (it's on by
default), pine adds the attribute format=flowed to the Content-Type
header and then proceeds to massage the text to adhere to some RFC
standards about flowed text.
The pine docs state that flowed-text on sent messages can be disabled
on a per-message basis by hitting ^V after ^X but before confirming
the send - and that is when I hit this bug. What really happened is
that while the format=flowed attribute went away, the message _still_
got mangled.
(A patch submission mangled in this way by pine still "looks" normal,
but due to pine's prepending extraneous whitespace on various lines of
text, the patch is wrecked.)
-Mike
[...]
--- End Message ---
