From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/4] drop Date::Parse dependency
Date: Fri, 29 Nov 2019 12:25:04 +0000 [thread overview]
Message-ID: <20191129122508.7708-1-e@80x24.org> (raw)
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
next reply other threads:[~2019-11-29 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 12:25 Eric Wong [this message]
2019-11-29 12:25 ` [PATCH 1/4] git: async batch interface Eric Wong
2019-11-29 12:25 ` [PATCH 2/4] add msgtime_cmp maintainer test Eric Wong
2019-11-29 12:25 ` [PATCH 3/4] msgtime: drop Date::Parse for RFC2822 Eric Wong
2019-11-29 12:25 ` [PATCH 4/4] Date::Parse is now optional Eric Wong
2019-12-01 22:04 ` [PATCH 5/4] msgtime: avoid obviously out-of-range dates (for now) Eric Wong
2019-12-12 3:42 ` Eric Wong
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: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191129122508.7708-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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/public-inbox.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).