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

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

From
Jeff King <peff@peff.net>
Date
Apr 7, 2009, 21:51 UTC
Message-ID
<20090407215143.GA18144@coredump.intra.peff.net>
In-Reply-To
<1239139522-24118-1-git-send-email-mfwitten@gmail.com>
On Tue, Apr 07, 2009 at 04:25:17PM -0500, Michael Witten wrote:
Show 10 quoted lines
> When sending a patch series, the emails often arrive at the final
> destination out of order; though these emails should be chained
> via the In-Reply-To headers, some mail-viewing systems display
> by order of arrival instead.
> 
> The --delay option provides a means for specifying that there
> should be a certain number of seconds of delay between sending
> emails, so that the arrival order can be controlled better.
> 
> Signed-off-by: Michael Witten <mfwitten@gmail.com>

I'm a little dubious how well this works in practice. Have you done any experiments?

The reason I am dubious is that you are presumably delaying only a few seconds (since anything more would be quite annoying to the user). This may deal with a short race condition in your local mail server. But what is the real cause of out-of-order delivery? Is it the local mail server seeing two messages essentially "simultaneously" and then reordering them randomly? Or is it other random delays that happen _after_ that, like network congestion, DNS lookups, down or congested servers, time it takes to deliver the actual message body (e.g., if your mail server sends two simultaneously, but the first one is much larger and takes longer to complete), etc.

Those delays can be much larger than a few seconds, and this won't help at all there.

I think it may still be reasonable to implement a solution that only covers some of the cases, but I what I am asking is if we know what percentage of the cases that is. If we are preventing only 1% of out-of-order deliveries with this, I question whether it is worth the bother.

-Peff
Previous: Michael WittenNext: Nicolas Sebrecht
Message 25 of 30 in “send-email: Add --delay for separating emails”
  1. 1/6 send-email: Add --delay for separating emailsMichael Witten, Apr 7, 2009
  2. 2/6 send-email: --smtp-server-port should take an integerMichael Witten, Apr 7, 2009
  3. 3/6 send-email: Handle "GIT:" rather than "GIT: " during --composeMichael Witten, Apr 7, 2009
  4. 4/6 send-email: --compose takes optional argument to existing fileMichael Witten, Apr 7, 2009
  5. 5/6 send-email: Cleanup the usage text a bitMichael Witten, Apr 7, 2009
  6. 6/6 send-email: Remove horrible mix of tabs and spacesMichael Witten, Apr 7, 2009
  7. demerphqApr 7, 2009
  8. Michael WittenApr 7, 2009
  9. demerphqApr 7, 2009
  10. demerphqApr 7, 2009
  11. Jeff KingApr 7, 2009
  12. Andreas EricssonApr 7, 2009
  13. Tomas CarneckyApr 7, 2009
  14. Jeff KingApr 8, 2009
  15. Junio C HamanoApr 11, 2009
  16. Junio C HamanoApr 11, 2009
  17. Junio C HamanoApr 11, 2009
  18. Michael WittenApr 11, 2009
  19. Junio C HamanoApr 12, 2009
  20. Michael WittenApr 12, 2009
  21. Junio C HamanoApr 7, 2009
  22. Junio C HamanoApr 11, 2009
  23. Wesley J. LandakerApr 11, 2009
  24. Michael WittenApr 11, 2009
  25. Jeff KingApr 7, 2009
  26. 1/6 Re: send-email: Add --delay for separating emailsNicolas Sebrecht, Apr 7, 2009
  27. Andreas EricssonApr 7, 2009
  28. Jeff KingApr 8, 2009
  29. Jeff KingApr 8, 2009
  30. Junio C HamanoApr 7, 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.