git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] send-email: new option to walkaround email server limits

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 2, 2017, 09:58 UTC
Message-ID
<CACBZZX6fursxEaBGr9raz+x8qBm0WZrmHCkMbtpajRzOM3B6qA@mail.gmail.com>
In-Reply-To
<743D62FA-65B9-4DCC-978E-DAF442AE0B0D@163.com>
On Mon, May 1, 2017 at 8:03 AM, 赵小强 <zxq_yx_007@163.com> wrote:
Show 17 quoted lines
>
> Thanks for your reply , Junio !
>
>> 在 2017年5月1日,09:54,Junio C Hamano <gitster@pobox.com> 写道:
>>
>> here.  We need to find a better name for the option.  Perhaps
>>   "--batch-size=<num>", "--max-messages-per-connection=<num>" or
>>   something?
>>
>
> --batch-size is ok with me
>
>> - The code seems to do the "logging out and the logging back in"
>>   dance without any delay in between.  Is it something we want to
>>   consider to add a small (possibly configurable) delay in between?
>
> It' s a good idea to have a configurable delay.

It makes sense to have a configurable delay for git-send-email unrelated to this option, I'd use a facility like that.

A lot of mail clients just sort based on date/msgid or whatever not date/subject, so the rapid-fire output of send-email often arrives out of order because it's all sent at the same second. I'd use some option where I could send a series as "all" and have it sleep(N) in between sending mails.

Previous: 赵小强Next: Junio C Hamano
Message 4 of 9 in “send-email: new option to walkaround email server limits”
  1. send-email: new option to walkaround email server limitsxiaoqiang zhao, Apr 29, 2017
  2. Junio C HamanoMay 1, 2017
  3. 赵小强May 1, 2017
  4. Ævar Arnfjörð BjarmasonMay 2, 2017
  5. Junio C HamanoMay 4, 2017
  6. Ramkumar RamachandraMay 4, 2017
  7. Ævar Arnfjörð BjarmasonMay 4, 2017
  8. Paolo BonziniMay 2, 2017
  9. 赵小强May 4, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.