On 18.04.2018 02:54, Eric Wong wrote:
> Stefan Agner wrote:
>> This addresses the issue reported here:
>> https://public-inbox.org/git/997160314bbafb3088a401f1c09cc...@agner.ch/
>
> Thanks for bringing this up.
>
>> --- a/git-send-email.perl
>> +++ b/git-sen
-3.6
Avoid the second pair by reading the current headers into the
appropriate variables.
Signed-off-by: Stefan Agner
---
This addresses the issue reported here:
https://public-inbox.org/git/997160314bbafb3088a401f1c09cc...@agner.ch/
git-send-email.perl | 7 ++-
1 file changed, 6 insertions
Hi,
Using git format-patch --thread + send-mail leads to
In-Reply-To/References headers added twice (with the very same value).
This is not allowed according to RFC 5322 Section 3.6:
https://tools.ietf.org/html/rfc5322#section-3.6
Ideally probably git-format-patch should be smart about whether
In
On 2015-09-30 10:51, Junio C Hamano wrote:
> Lars Wendler writes:
>
>> It seems to me that there is a size limit, after cutting down the patch
>> to ~16K, sending started to work. I cut it twice, once by removing lines
>> from the head and once from the bottom, in both cases at the size of
>> aro
On 2015-09-30 10:51, Junio C Hamano wrote:
> Lars Wendler writes:
>
>> It seems to me that there is a size limit, after cutting down the patch
>> to ~16K, sending started to work. I cut it twice, once by removing lines
>> from the head and once from the bottom, in both cases at the size of
>> aro
On 2015-07-24 14:59, Stefan Agner wrote:
> Hi Juston,
>
> On 2015-07-15 07:11, Juston Li wrote:
>> Recently, I have had trouble using git send-email to send a patchset.
>> After the confirmation to send the email I get the following:
>> Send this email? ([y]es|[n]o|[q]
Hi Juston,
On 2015-07-15 07:11, Juston Li wrote:
> Recently, I have had trouble using git send-email to send a patchset.
> After the confirmation to send the email I get the following:
> Send this email? ([y]es|[n]o|[q]uit|[a]ll): y
> [Net::SMTP::SSL] Connection closed at /usr/lib/git-core/git-sen
7 matches
Mail list logo
