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

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

From
NSNicolas Sebrecht <nicolas.s-dev@laposte.net>
Date
Apr 9, 2009, 17:45 UTC
Message-ID
<20090409174547.GA15767@vidovic>
In-Reply-To
<b4087cc50904091027l4656a6adv6a72bad0a747cdc1@mail.gmail.com>
On Thu, Apr 09, 2009 at 12:27:18PM -0500, Michael Witten wrote:
Show 12 quoted lines
> 
> On Thu, Apr 9, 2009 at 11:17, Nicolas Sebrecht
> <nicolas.s-dev@laposte.net> wrote:
> >
> > 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.

But we could forbid the use of --delay with non-chained emails, no? Or at least, warn it should not be used.

-- 
Nicolas Sebrecht
Previous: Michael WittenNext: Michael Witten
Message 14 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.