git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 14, 2019, 11:31 UTC
Message-ID
<nycvar.QRO.7.76.6.1903141228510.41@tvgsbejvaqbjf.bet>
In-Reply-To
<20190313201854.GA5530@sigill.intra.peff.net>
Hi Peff,
On Wed, 13 Mar 2019, Jeff King wrote:
Show 32 quoted lines
> On Wed, Mar 13, 2019 at 03:39:09PM -0400, Jeff King wrote:
> 
> > 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.
> 
> 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.

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.

Ciao, Dscho

Previous: Jeff KingNext: Jeff King
Message 8 of 28 in “point pull requesters to Git Git Gadget”
  1. point pull requesters to Git Git GadgetJeff King, Mar 12, 2019
  2. Roberto TyleyMar 12, 2019
  3. Jeff KingMar 13, 2019
  4. Johannes SchindelinMar 13, 2019
  5. Junio C HamanoMar 13, 2019
  6. Jeff KingMar 13, 2019
  7. Jeff KingMar 13, 2019
  8. Johannes SchindelinMar 14, 2019
  9. Jeff KingMar 15, 2019
  10. Johannes SchindelinMar 15, 2019
  11. Jeff KingMar 15, 2019
  12. Junio C HamanoMar 18, 2019
  13. Jeff KingMar 18, 2019
  14. Thomas GummererMar 18, 2019
  15. Jeff KingMar 18, 2019
  16. Junio C HamanoMar 19, 2019
  17. Ævar Arnfjörð BjarmasonMar 18, 2019
  18. Johannes SchindelinMar 13, 2019
  19. Junio C HamanoMar 13, 2019
  20. Junio C HamanoMar 13, 2019
  21. Junio C HamanoMar 13, 2019
  22. Jeff KingMar 13, 2019
  23. GitGitGadget on github.com/git/git?, was Re: [RFC/PATCH] point pull requesters to Git Git GadgetJohannes Schindelin, Mar 14, 2019
  24. Duy NguyenMar 14, 2019
  25. Jeff KingMar 15, 2019
  26. Johannes SchindelinMar 15, 2019
  27. Ævar Arnfjörð BjarmasonMar 15, 2019
  28. Jeff KingMar 15, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.