From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: 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: Thu, 14 Mar 2019 07:17:45 +0900 [thread overview]
Message-ID: <xmqq36nqe7w6.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190313193909.GB3400@sigill.intra.peff.net> (Jeff King's message of "Wed, 13 Mar 2019 15:39:09 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Mar 13, 2019 at 10:49:22AM +0900, Junio C Hamano wrote:
>
>> Jeff King <peff@peff.net> writes:
>>
>> > infrequent contributors. And there are a few reasons to prefer GGG:
>> >
>> > 1. submitGit seems to still have a few rough edges. E.g., it doesn't
>> > munge timestamps to help threaded mail readers handled out-of-order
>> > delivery.
>>
>> Hmph, I had an impression that the recent "why aren't these sorted"
>> topics were via GGG, not submitGit, though.
>
> We did have one case a few months ago, but I think it was since fixed.
>
> Whereas it cannot be fixed for submitGit without major re-architecting,
> because the mails go out through Amazon SES, which writes its own
> timestamp.
>
> I could be wrong about GGG being fixed though. I haven't noticed the
> problem lately, but we definitely had a submitGit-related one a few
> weeks ago.
Yeah, I was confused; <xmqqtvgk4urv.fsf@gitster-ct.c.googlers.com>
was about submitGit, but somehow I thought the sender switched to,
and the out-of-order thread was sent via, GGG. My mistake.
next prev parent reply other threads:[~2019-03-13 22:17 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
2019-03-13 21:05 ` Johannes Schindelin
2019-03-13 22:17 ` Junio C Hamano [this message]
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=xmqq36nqe7w6.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).