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
Nicolas Pitre <nico@cam.org>
Date
Apr 9, 2009, 17:48 UTC
Message-ID
<alpine.LFD.2.00.0904091342170.6741@xanadu.home>
In-Reply-To
<20090409081443.GB17221@coredump.intra.peff.net>
On Thu, 9 Apr 2009, Jeff King wrote:
Show 8 quoted lines
> On Wed, Apr 08, 2009 at 09:25:25AM -0500, Michael Witten wrote:
> 
> > Firstly, I presume that someone is electing to use this option, so it is
> > almost by definition not annoying for that person.
> 
> Sure, obviously only people who enable it will be affected. I was
> thinking of it more in terms of group economics: how many people _will_
> enable it, because they think the payoff outweighs the annoyance.

My ISP doesn't allow me to send more than 20 emails at once. So if a patch series has more than 20 patches, send-email will be denied the sending of the end of the series, which is rather anoying.

I didn't test this option (have no large patch series to post at the moment), but if it could allow me to easily work around the ISP restriction then I would be happy.

Nicolas
Previous: Nicolas PitreNext: Junio C Hamano
Message 6 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.