From: Michael Witten <mfwitten@gmail.com>
To: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH RFC 1/6] Re: send-email: Add --delay for separating emails
Date: Thu, 9 Apr 2009 12:38:15 -0500 [thread overview]
Message-ID: <b4087cc50904091038v46f7f42bj844ba3a87ee28821@mail.gmail.com> (raw)
In-Reply-To: <b4087cc50904091027l4656a6adv6a72bad0a747cdc1@mail.gmail.com>
On Thu, Apr 9, 2009 at 12:27, Michael Witten <mfwitten@gmail.com> wrote:
> 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. 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.
I do agree that --delay could exacerbate the spreading out of patches.
next prev parent reply other threads:[~2009-04-09 17:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 14:25 [PATCH RFC 1/6] send-email: Add --delay for separating emails Michael Witten
2009-04-08 14:35 ` Michael Witten
2009-04-09 8:14 ` Jeff King
2009-04-09 8:49 ` Junio C Hamano
2009-04-09 17:51 ` Nicolas Pitre
2009-04-09 17:48 ` Nicolas Pitre
2009-04-09 19:28 ` Junio C Hamano
2009-04-09 19:36 ` Nicolas Pitre
2009-04-09 20:59 ` Michael Witten
2009-04-09 21:02 ` Michael Witten
2009-04-09 16:17 ` [PATCH RFC 1/6] " Nicolas Sebrecht
2009-04-09 17:27 ` Michael Witten
2009-04-09 17:38 ` Michael Witten [this message]
2009-04-09 17:45 ` Nicolas Sebrecht
2009-04-09 18:43 ` Michael Witten
-- strict thread matches above, loose matches on Subject: below --
2009-04-07 21:25 [PATCH RFC 1/6] " Michael Witten
2009-04-07 21:51 ` Jeff King
2009-04-07 22:08 ` [PATCH RFC 1/6] " Nicolas Sebrecht
2009-04-07 22:17 ` Andreas Ericsson
2009-04-08 6:05 ` Jeff King
2009-04-08 6:03 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4087cc50904091038v46f7f42bj844ba3a87ee28821@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=git@vger.kernel.org \
--cc=nicolas.s-dev@laposte.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).