On 2018-02-21 14:37, Corinna Vinschen wrote: > On Feb 21 14:20, Brian Inglis wrote: >> On 2018-02-21 14:05, Corinna Vinschen wrote: >>> Hi David, >>> >>> On Feb 21 18:09, David Macek wrote: >>>> --- >>>> winsup/doc/ntsec.xml | 2 +- >>>> 1 file changed, 1 insertion(+), 1 deletion(-) >>>> >>>> diff --git a/winsup/doc/ntsec.xml b/winsup/doc/ntsec.xml >>>> index df1d54930..03293591b 100644 >>>> --- a/winsup/doc/ntsec.xml >>>> +++ b/winsup/doc/ntsec.xml >>>> @@ -914,7 +914,7 @@ This is not valid: >>>> </screen> >>>> <para> >>>> -Apart from this restriction, the reminder of the line can have as >>>> +Apart from this restriction, the remainder of the line can have as >>>> many spaces and TABs as you like. >>>> </para> >>>> -- >>>> 2.16.2.windows.1 >>> >>> The patch is malformed. It claims to contain 7 lines (6 lines context, >>> one line changed), but actually it has only 4 lines context. Please >>> check your git settings. >> >> "It's an een-justice!" -- Calimero >> Check your mail client blank line squishing settings; I see: > > I'm using mutt which is usually sticks to the original. I checked again > and when looking into the message with vi I see this: > > </screen> > =20=20 > <para> > [...] > </para> > =20=20 > > Why are the spaces decodes as =20 in these two lines? > > In theory the decode-copy command should retain the empty lines > and it did so before. Why not now?!?
I see exactly the same in TB view source, but the message appears as expected. I can see why you strenuously request git format-patch/send-email attachments ;^> -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
