[PATCH v2 0/4] Automatic transfer encoding for patches
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Jul 8, 2018, 22:17 UTC
- Message-ID
- <20180708221713.518276-1-sandals@crustytoothpaste.net>
- In-Reply-To
- <20180706022357.739657-1-sandals@crustytoothpaste.net>
This series introduces an "auto" value for git send-email --transfer-encoding that uses 8bit when possible (i.e. when lines are 998 octets or shorter) and quoted-printable otherwise; it then makes this the default behavior. It also makes --validate aware of transfer encoding so it doesn't complain when using quoted-printable or base64.
Changes from v1: * Update commit messages to refer to RFC 5322. * Add a missing space. * Remove the needless capture of stderr. * Define "suitable transfer encoding". * Invert test to better capture failures. * Wrap --validate code in an if block instead of returning early. * Update documentation to reflect correct, modern RFC.
brian m. carlson (4): send-email: add an auto option for transfer encoding send-email: accept long lines with suitable transfer encoding send-email: automatically determine transfer-encoding docs: correct RFC specifying email line length
Documentation/git-send-email.txt | 17 ++++++---- git-send-email.perl | 46 +++++++++++++------------- t/t9001-send-email.sh | 57 ++++++++++++++++++++++++++++++++ 3 files changed, 91 insertions(+), 29 deletions(-)