From: Sean Neakums <sneakums@zork.net>
To: linux-kernel@vger.kernel.org
Subject: [OT] Re: Rootfs mounted from user space - problem with umount
Date: Sun, 30 Nov 2003 00:38:42 +0000 [thread overview]
Message-ID: <6u8ylyofl9.fsf_-_@zork.zork.net> (raw)
In-Reply-To: <3FC912D5.7030705@undead.cc> (John Zielinski's message of "Sat, 29 Nov 2003 16:42:45 -0500")
John Zielinski <grim@undead.cc> writes:
> Sean Neakums wrote:
>
>>I don't think so; it's mangled here in Gnus, too.
>
> Can you check the message source or save the mail to your HD and see
> if it's mangled there as well? The lines that cause the problems have
> an extra space at the end of them. But that's how the were in my
> original patch file. I forwarded that message to myself and checked
> that actual file on my mail server and the patch was 100% like the
> original. It _is_ a display bug.
You're right, the patch looks fine in the raw message. However, the
message's Content-Type header specifies "format=flowed", and according
to RFC 2646, if a line ends in one or more spaces, it is to be flowed
(sec 4.2, paragraph 3). So it is not a display bug.
next prev parent reply other threads:[~2003-11-30 0:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 5:24 Rootfs mounted from user space - problem with umount John Zielinski
2003-11-29 5:31 ` William Lee Irwin III
2003-11-29 6:14 ` John Zielinski
2003-11-29 6:21 ` William Lee Irwin III
2003-11-29 9:40 ` John Zielinski
2003-11-29 9:44 ` William Lee Irwin III
2003-11-29 20:02 ` John Zielinski
2003-11-29 20:20 ` John Zielinski
2003-11-29 20:25 ` William Lee Irwin III
2003-11-29 21:05 ` John Zielinski
2003-11-29 21:17 ` Sean Neakums
2003-11-29 21:42 ` John Zielinski
2003-11-30 0:38 ` Sean Neakums [this message]
2003-11-29 5:38 ` Valdis.Kletnieks
2003-11-29 6:25 ` John Zielinski
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=6u8ylyofl9.fsf_-_@zork.zork.net \
--to=sneakums@zork.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).