Re: [RFC/PATCH] point pull requesters to Git Git Gadget

From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
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: Fri, 15 Mar 2019 14:42:42 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1903151427460.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20190315031948.GD28943@sigill.intra.peff.net>

Hi Peff,

On Thu, 14 Mar 2019, Jeff King wrote:

> 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.

Fine, I'll put that on my backlog:
https://github.com/gitgitgadget/gitgitgadget/issues/81

> 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. ;)

Indeed. And you remind me: I wanted to disallow annoyingly large patch
series: https://github.com/gitgitgadget/gitgitgadget/issues/82

Another thing that I always dreamed of having: GitGitGadget could
automatically warn about commit messages that are incomplete, that
disagree with our preferred format, that contain typos or offensive
language.

Likewise, I had this idea that once we had some robust Clang format
definition, GitGitGadget could verify that the patches conform to what we
want, and automatically generate fixed branches if not.

Basically, all the automation I can get, to relieve humans from tasks that
machines can do.

Children can have dreams, can't they ;-)

Ciao,
Dscho