Re: [PATCH 2/3] send-email: accept long lines with suitable transfer encoding

2018-07-06 Thread brian m. carlson
On Fri, Jul 06, 2018 at 08:26:04AM -0400, Drew DeVault wrote: > On 2018-07-06 2:23 AM, brian m. carlson wrote: > > diff --git a/git-send-email.perl b/git-send-email.perl > > index a76953c310..4ea30c4070 100755 > > --- a/git-send-email.perl > > +++ b/git-send-email.perl > > @@ -1899,6 +1899,10 @@

Re: [PATCH 2/3] send-email: accept long lines with suitable transfer encoding

2018-07-06 Thread Drew DeVault
On 2018-07-06 2:23 AM, brian m. carlson wrote: > diff --git a/git-send-email.perl b/git-send-email.perl > index a76953c310..4ea30c4070 100755 > --- a/git-send-email.perl > +++ b/git-send-email.perl > @@ -1899,6 +1899,10 @@ sub validate_patch { > return $hook_error if $hook_error; >

Re: [PATCH 2/3] send-email: accept long lines with suitable transfer encoding

2018-07-06 Thread Eric Sunshine
On Thu, Jul 5, 2018 at 10:24 PM brian m. carlson wrote: > With --validate (which is the default), we warn about lines exceeding > 998 characters due to the limits specified in RFC 5321. However, if > we're using a suitable transfer encoding (quoted-printable or base64), > we're guaranteed not to

[PATCH 2/3] send-email: accept long lines with suitable transfer encoding

2018-07-05 Thread brian m. carlson
With --validate (which is the default), we warn about lines exceeding 998 characters due to the limits specified in RFC 5321. However, if we're using a suitable transfer encoding (quoted-printable or base64), we're guaranteed not to have lines exceeding 76 characters, so there's no need to fail