Re: Please make git-am handle \r\n-damaged patches
From: Erik Faye-Lund <hidden>
Date: 2016-06-15 22:47:09
Possibly related (same subject, not in this thread)
- 2016-06-15 · Please make git-am handle \r\n-damaged patches · "H. Peter Anvin" <hpa@zytor.com>
- 2016-06-15 · Re: Please make git-am handle \r\n-damaged patches · Junio C Hamano <hidden>
- 2016-06-15 · Re: Please make git-am handle \r\n-damaged patches · Wesley J. Landaker <hidden>
- 2016-06-15 · Re: Please make git-am handle \r\n-damaged patches · "H. Peter Anvin" <hpa@zytor.com>
- 2016-06-15 · Re: Please make git-am handle \r\n-damaged patches · Sverre Rabbelier <hidden>
On Tue, Aug 4, 2009 at 8:46 AM, Junio C Hamano[off-list ref] wrote:
I thought about this approach, but it made me worried about a case where an otherwise sane piece of e-mail has \r at the end of one line as the real payload. But as long as we are talking about a text e-mail (and we are talking about mailsplit here and a binary payload with a CTE applied counts as text), I think we can safely use an approach like this.
RFC 2822, section 2.3 explicitly states that a CR should not occur without a LF (and vice versa, but the e-mail client might convert CRLF to LF when saving to file), so I think this should be safe. -- Erik "kusma" Faye-Lund kusmabite@gmail.com (+47) 986 59 656