I started working on the async batch interface for git many months ago, but didn't have a good use case for it. The comparison test in msgtime_cmp gives me an excuse to start using it :)
Spam email I don't care about, but there's some differences for folks that send valid mails: The new code gets tripped up by 4 digit dates from non-sensical times (emails from 1904, really?), so maybe some adjustment is necessary. There's also some bogus dates from the year 71685, so that's a case where falling back on the Received: header is a good choice. Maybe some more odd caes when checks are done running... Eric Wong (4): git: async batch interface add msgtime_cmp maintainer test msgtime: drop Date::Parse for RFC2822 Date::Parse is now optional INSTALL | 9 ++- MANIFEST | 2 + Makefile.PL | 1 - TODO | 4 - ci/deps.perl | 2 +- lib/PublicInbox/Admin.pm | 2 +- lib/PublicInbox/Git.pm | 94 +++++++++++++++++----- lib/PublicInbox/MDA.pm | 5 +- lib/PublicInbox/MsgTime.pm | 118 +++++++++++++++++++++++---- t/msgtime.t | 7 ++ xt/git_async_cmp.t | 61 ++++++++++++++ xt/msgtime_cmp.t | 161 +++++++++++++++++++++++++++++++++++++ 12 files changed, 415 insertions(+), 51 deletions(-) create mode 100644 xt/git_async_cmp.t create mode 100644 xt/msgtime_cmp.t -- unsubscribe: meta+unsubscr...@public-inbox.org archive: https://public-inbox.org/meta/
