From: Michael Witten <mfwitten@gmail.com>
To: Jeff King <peff@peff.net>,
Nicolas Sebrecht <nicolas.s-dev@laposte.net>,
Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH RFC 1/6] send-email: Add --delay for separating emails
Date: Wed, 8 Apr 2009 09:35:02 -0500 [thread overview]
Message-ID: <b4087cc50904080735i6d56212fke3072a22da488fb@mail.gmail.com> (raw)
In-Reply-To: <49dcb464.06d7720a.66ca.ffffbd30@mx.google.com>
On Wed, Apr 8, 2009 at 09:25, Michael Witten <mfwitten@gmail.com> wrote:
> For instance, with
> a 14-patch series, one could set `--delay 60' and then let send-email
> run happily for the next 14 minutes with nary a thought.
As implemented, it would only take 13 minutes.
For a 5-patch series:
* Patch 1/5 sent
* delay 60 seconds
* Patch 2/5 sent
* delay 60 seconds
* Patch 3/5 sent
* delay 60 seconds
* Patch 4/5 sent
* delay 60 seconds
* Patch 5/5 sent
* send email exits immediately
next prev parent reply other threads:[~2009-04-08 14:36 UTC|newest]
Thread overview: 18+ 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 [this message]
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
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 23:17 ` Junio C Hamano
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=b4087cc50904080735i6d56212fke3072a22da488fb@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nicolas.s-dev@laposte.net \
--cc=peff@peff.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).