> On Sat, Nov 30, 2019 at 4:14 PM Jonathan Corbet <corbet@lwn.net> wrote:
> >
> > So my tooling is "git am", nothing special.
> >
> > All of the afflicted files arrived in that state as the result of a pair
> > of patches from Jonathan (copied); I have verified that the original
> > patches also had the DOS line endings.
> >
> > The problem repeats if I apply those patches now, even if I add an
> > explicit "--no-keep-cr" to the "git am" command line.  It seems like maybe
> > my version of git is somehow broken?  I have git-2.21.0-1.fc30.x86_64,
> > FWIW.  
> 
> Hmm. I wonder if the CRLF removal is broken in general, or if the
> emails are somehow unusual (patches in attachments or MIME-encoded or
> something)? Maybe the CRLF was removed from the envelope email lines,
> but if the patch is then decoded from an attachment or something it's
> not removed again from there?
> 
> Can you attach (not forward) one of the (raw) emails that shows the
> problem and keep the git mailing list cc'd?

Attached.  The patch itself was not an attachment, but it was
base64-encoded. 

jon