Re: [PATCH] send-email: handle adjacent RFC 2047-encoded words properly

2014-11-24 Thread Jeff King
On Mon, Nov 24, 2014 at 09:26:22PM +0300, Роман Донченко wrote: > Yeah, I did realize that token is more restrictive than encoded-text, but I > didn't want to stray too far from the subject line of the patch. What I'll > probably do is split the patch into two, one for regex tweaking and one for >

Re: [PATCH] send-email: handle adjacent RFC 2047-encoded words properly

2014-11-24 Thread Роман Донченко
Jeff King писал в своём письме Mon, 24 Nov 2014 18:36:09 +0300: On Mon, Nov 24, 2014 at 02:50:04AM +0300, Роман Донченко wrote: The RFC says that they are to be concatenated after decoding (i.e. the intervening whitespace is ignored). I change the sender's name to an all-Cyrillic string in

Re: [PATCH] send-email: handle adjacent RFC 2047-encoded words properly

2014-11-24 Thread Роман Донченко
Junio C Hamano писал в своём письме Mon, 24 Nov 2014 10:27:51 +0300: On Sun, Nov 23, 2014 at 3:50 PM, Роман Донченко wrote: The RFC says that they are to be concatenated after decoding (i.e. the intervening whitespace is ignored). I change the sender's name to an all-Cyrillic string in th

Re: [PATCH] send-email: handle adjacent RFC 2047-encoded words properly

2014-11-24 Thread Jeff King
On Sun, Nov 23, 2014 at 11:27:51PM -0800, Junio C Hamano wrote: > Was the change to the test to use Cyrillic really necessary, or did it > suffice if you simply extended the existsing "Funny Name" spelled with > strange accents, but you substituted the whole string anyway? > > Until I found out w

Re: [PATCH] send-email: handle adjacent RFC 2047-encoded words properly

2014-11-24 Thread Jeff King
On Mon, Nov 24, 2014 at 02:50:04AM +0300, Роман Донченко wrote: > The RFC says that they are to be concatenated after decoding (i.e. the > intervening whitespace is ignored). > > I change the sender's name to an all-Cyrillic string in the tests so that > its encoded form goes over the 76 characte

Re: [PATCH] send-email: handle adjacent RFC 2047-encoded words properly

2014-11-23 Thread Junio C Hamano
On Sun, Nov 23, 2014 at 3:50 PM, Роман Донченко wrote: > The RFC says that they are to be concatenated after decoding (i.e. the > intervening whitespace is ignored). > > I change the sender's name to an all-Cyrillic string in the tests so that > its encoded form goes over the 76 characters in a li

[PATCH] send-email: handle adjacent RFC 2047-encoded words properly

2014-11-23 Thread Роман Донченко
The RFC says that they are to be concatenated after decoding (i.e. the intervening whitespace is ignored). I change the sender's name to an all-Cyrillic string in the tests so that its encoded form goes over the 76 characters in a line limit, forcing format-patch to split it into multiple encoded