Johannes Sixt <j.sixt@xxxxxxxxxxxxx> writes: > You are right here. My thought was that even though the recipient gets a > broken patch, he would be able to fix it up. This may be acceptable for > peer-to-peer communication, but not for a development style that involves > many recipients. > > Then git-format-patch and log-family with --pretty=email -p could warn > about these candidates-to-be-broken patches. I'd rather not, unless it is explicitly asked for by a separate command line option. Transferring over SMTP is not the only (nor even primary) use of format-patch output. On the other hand, git-send-email _is_ all about SMTP transfer. Perhaps a loop over input files upfront to check the line length limit, and warn if there are suspiciously long lines even before sending the first piece of e-mail out, would be a reasonable approach. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
