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

Re: [PATCH RFC 1/6] Re: send-email: Add --delay for separating emails

From
Michael Witten <mfwitten@gmail.com>
Date
Apr 9, 2009, 17:27 UTC
Message-ID
<b4087cc50904091027l4656a6adv6a72bad0a747cdc1@mail.gmail.com>
In-Reply-To
<20090409161756.GA12910@vidovic>

On Thu, Apr 9, 2009 at 11:17, Nicolas Sebrecht <nicolas.s-dev@laposte.net> wrote:

Show 7 quoted lines
>
> The --delay option may have an undesirable side effect. In case of
> non-chained emails, unrelated mails could be insterted between patches
> where *all* MUA would be affected. It's not only true for very high
> volume message mailing-lists (million monkeys receiving...). FMPOV, it's
> worse than all display issues we already know or have with the current
> behaviour.

But it's already impossible to protect against this scenario. In that situation, the smallest delay possible is desired, so --delay wouldn't even be used (that is, its value would be zero). However, the transit delay could never be small enough to guarantee that no other emails are inserted into the patch series, so the only solution is to chain them. At this point, we're back to the problem of arrival time, and hence --delay becomes useful.

:-D
Previous: Nicolas SebrechtNext: Michael Witten
Message 12 of 15 in “Re: [PATCH RFC 1/6] send-email: Add --delay for separating emails”
  1. Michael WittenApr 8, 2009
  2. Michael WittenApr 8, 2009
  3. Jeff KingApr 9, 2009
  4. Junio C HamanoApr 9, 2009
  5. Nicolas PitreApr 9, 2009
  6. Nicolas PitreApr 9, 2009
  7. Junio C HamanoApr 9, 2009
  8. Nicolas PitreApr 9, 2009
  9. Michael WittenApr 9, 2009
  10. Michael WittenApr 9, 2009
  11. 1/6 Re: send-email: Add --delay for separating emailsNicolas Sebrecht, Apr 9, 2009
  12. Michael WittenApr 9, 2009
  13. Michael WittenApr 9, 2009
  14. 1/6 Re: send-email: Add --delay for separating emailsNicolas Sebrecht, Apr 9, 2009
  15. Michael WittenApr 9, 2009

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.