From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Roberto Tyley <roberto.tyley@gmail.com>
Subject: Re: [RFC/PATCH] point pull requesters to Git Git Gadget
Date: Thu, 14 Mar 2019 23:19:48 -0400 [thread overview]
Message-ID: <20190315031948.GD28943@sigill.intra.peff.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1903141228510.41@tvgsbejvaqbjf.bet>
On Thu, Mar 14, 2019 at 12:31:21PM +0100, Johannes Schindelin wrote:
> > Hmm. I guess it is still an issue in GGG. This thread has identical
> > timestamps on patches 1 and 2 (and my server received them out of order
> > by 2 seconds, so mutt orders them wrong):
> >
> > https://public-inbox.org/git/pull.163.git.gitgitgadget@gmail.com/
> >
> > I do still think GGG has a more feasible path forward on this particular
> > bug, though.
>
> Indeed. And it is a bug^Wfeature of GMail, I guess, that it knows better
> and ignores the Date: header of the mbox fed to it.
Heh. So it in fact has the identical problem that submitGit and SES
have. :)
> The only workaround I can think of is to introduce ugly one-second-sleeps.
> I will do that if it proves necessary, but I do have a problem right now
> because my only GitGitGadget reviewer (Stolee) is kinda busy with other
> things for the time being.
I suspect that may be the ultimate solution. Which isn't fantastic, but
at the same time, I doubt anybody would really notice that much. There
are typically delays of seconds to minutes already in delivering email.
Unless somebody has a 200 patch series, but maybe then it is kinder to the
receivers to let it trickle in. ;)
-Peff
next prev parent reply other threads:[~2019-03-15 3:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:32 [RFC/PATCH] point pull requesters to Git Git Gadget Jeff King
2019-03-12 23:08 ` Roberto Tyley
2019-03-13 19:34 ` Jeff King
2019-03-13 20:50 ` Johannes Schindelin
2019-03-13 1:49 ` Junio C Hamano
2019-03-13 19:39 ` Jeff King
2019-03-13 20:18 ` Jeff King
2019-03-14 11:31 ` Johannes Schindelin
2019-03-15 3:19 ` Jeff King [this message]
2019-03-15 13:42 ` Johannes Schindelin
2019-03-15 18:43 ` Jeff King
2019-03-18 2:52 ` Junio C Hamano
2019-03-18 21:12 ` Jeff King
2019-03-18 21:48 ` Thomas Gummerer
2019-03-18 21:52 ` Jeff King
2019-03-19 0:30 ` Junio C Hamano
2019-03-18 22:25 ` Ævar Arnfjörð Bjarmason
2019-03-13 21:05 ` Johannes Schindelin
2019-03-13 22:17 ` Junio C Hamano
2019-03-13 2:07 ` Junio C Hamano
2019-03-13 2:18 ` Junio C Hamano
2019-03-13 19:39 ` Jeff King
2019-03-14 12:04 ` GitGitGadget on github.com/git/git?, was " Johannes Schindelin
2019-03-14 14:46 ` Duy Nguyen
2019-03-15 3:30 ` Jeff King
2019-03-15 14:51 ` Johannes Schindelin
2019-03-15 16:28 ` Ævar Arnfjörð Bjarmason
2019-03-15 18:41 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190315031948.GD28943@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=roberto.tyley@gmail.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.