Ævar Arnfjörð Bjarmason <[email protected]> wrote:
> Good point. I also see that (via git log --author=Ævar --grep='^\[PATCH
> ') that this series itself arrived out of order (0 -> 2 -> 1), but I
> don't know to what extent public-inbox itself might be batching things.
public-inbox doesn't batch, aside from when the
public-inbox-watch process gets restarted and needs to catch up
using readdir. Once it's done catching up with readdir, it
gets into an inotify loop which injects messages in the order
the MTA (or offlineimap) puts them in a Maildir.
Right now, public-inbox only sorts by Date: header in the mail.
The next Xapian schema revision of public-inbox will use
internally sorts search results(*) by the date in the newest
Received: header. That is analogous to git committer date. The
displayed message date will still be sorted by the Date: header
(analogous to git author date); since git-send-email already
alters the Date: in a series for sorting.
This allow messages/threads which are actually new get bumped to
the top of the homepage; regardless of how wrong the original
sender's clock was.
It should help prevent kernel developers from crafting message
dates with optimization for classic^Wextra reviews in mind :)
(*) all the look-at-a-bunch-of-messages operations, including
the landing page (e.g. https://public-inbox.org/git/)
is a Xapian search query, nowadays; but "git log"