From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Roberto Tyley <roberto.tyley@gmail.com>
Subject: Re: [RFC/PATCH] point pull requesters to Git Git Gadget
Date: Mon, 18 Mar 2019 23:25:02 +0100 [thread overview]
Message-ID: <87h8bzes75.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20190318211215.GB29661@sigill.intra.peff.net>
On Mon, Mar 18 2019, Jeff King wrote:
> On Mon, Mar 18, 2019 at 11:52:54AM +0900, Junio C Hamano wrote:
>
>> Jeff King <peff@peff.net> writes:
>>
>> > 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.
>>
>> If the MSA is rewriting the timestamp (but why? Is the original
>> date "Wed, 13 Mar 2019 19:20:12 GMT" malformed or perhaps in the
>> future or something?), then there isn't much the sending program
>> can---'git send-email' would suffer from the same symptom.
>
> I think this statement from me is mid-way through my discovery of the
> actual issue. Yes, if the mail server is rewriting, the best we can do
> is put in an artificial sleep.
>
> It looks like GitGitGadget just uses normal SMTP to submit the messages.
> I wonder if normal people using gmail as their SMTP server for
> send-email also suffer from this. I've not ever noticed it, but I
> don't know how common that setup is.
It's the got-to setup for those of us using gmail & send-email. In
git-ml.git:
$ git ls-files | wc -l
371333
$ git grep -l '^\s+by smtp.gmail.com with ESMTPSA id ' | wc -l
35326
Roughly 1/2 of those are patches:
$ git grep --no-line-number -h -C30 '^\s+by smtp.gmail.com with ESMTPSA id ' |grep "^Subject: \[" | wc -l
14567
next prev parent reply other threads:[~2019-03-18 22:25 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
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 [this message]
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
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=87h8bzes75.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=peff@peff.net \
--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.
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).