On Mon, 2015-11-09 at 02:50 +0100, Ángel González wrote:
> Pete Biggs wrote:
> > > > > The Subject: line has a line feed in it.
> > > >
> > > > That's OK - in headers line feeds are allowed, the next line
> > > > needs to
> > > > be indented and it's treated as a single line *by mail aware
> > > >
Pete Biggs wrote:
> > > > The Subject: line has a line feed in it.
> > >
> > > That's OK - in headers line feeds are allowed, the next line
> > > needs to
> > > be indented and it's treated as a single line *by mail aware
> > > programs*.
> > > Unfortunately dos2unix doesn't know about anything ab
> > > The Subject: line has a line feed in it.
> >
> > That's OK - in headers line feeds are allowed, the next line needs to
> > be indented and it's treated as a single line *by mail aware programs*.
> > Unfortunately dos2unix doesn't know about anything about mail!
>
> Then we really need a a
On Fri, 2015-11-06 at 15:21 +, Joakim Tjernlund wrote:
> Saved the attached mail with an inline patch as a mbox
> and ran dos2unix(as I always do to strip away those pesky CR+NL)
> and the patch would not apply.
>
> The Subject: line has a line feed in it.
That's OK - in headers line feeds a
Saved the attached mail with an inline patch as a mbox
and ran dos2unix(as I always do to strip away those pesky CR+NL)
and the patch would not apply.
The Subject: line has a line feed in it.
This line also got line breaks:
@@ -2051,13 +2051,32 @@ static int __xipram
do_getlockstatus_oneblock(st
