git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Roberto Tyley <roberto.tyley@gmail.com>
Cc: "Christian Couder" <christian.couder@gmail.com>,
	git <git@vger.kernel.org>, "Jeff King" <peff@peff.net>,
	"Thomas Rast" <tr@thomasrast.ch>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Roberto Tyley" <robertotyley@gmail.com>
Subject: Re: [PATCH v2 0/9] Teach 'run' perf script to read config files
Date: Wed, 27 Sep 2017 09:04:18 +0900	[thread overview]
Message-ID: <xmqq4lrp9fct.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAFY1edZ6FX6s+H_XWa-=nKqr4NA9BNVxR6fcOo+5gn-Z1XKdUg@mail.gmail.com> (Roberto Tyley's message of "Tue, 26 Sep 2017 20:33:16 +0100")

Roberto Tyley <roberto.tyley@gmail.com> writes:

> I had a quick look at git-send-email.perl, I see the trick is the `time++` one
> introduced with https://github.com/git/git/commit/a5370b16 - seems reasonable!
>
> SubmitGit makes all emails in-reply-to the initial email, which I
> think is correct behaviour,
> but I can see that offsetting the times would probably give a more
> reliable sorting in
> a newsreader. ...
> ...so the only way SubmitGit can offset the times is to literally
> delay the sending of the emails,
> which is a bit unfortunate for patchbombs more than a few dozen commits long!

As this matters mostly for a series that is longer than several
patches, it indeed is unfortunate.  If SubmitGit needs to send and
sleep for a dozen messages, does it mean the end user has to wait 12
(or is it 11? ;-)) seconds?  If the human is the only thing that
needs waiting, it may be OK (after all, it all happens in the web
browser and the human can switch to other tasks after clicking
"submit"), but that may not be acceptable if this artificial delay
can cause a timeout in a moving part among many.

Thanks for looking into this.  

      parent reply	other threads:[~2017-09-27  0:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-23 19:39 [PATCH v2 0/9] Teach 'run' perf script to read config files Christian Couder
2017-09-24  7:59 ` Junio C Hamano
2017-09-26 15:40   ` Christian Couder
2017-09-26 19:33     ` Roberto Tyley
2017-09-26 19:38       ` Stefan Beller
2017-09-27  0:04       ` Junio C Hamano [this message]

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=xmqq4lrp9fct.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=roberto.tyley@gmail.com \
    --cc=robertotyley@gmail.com \
    --cc=tr@thomasrast.ch \
    /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).