user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/3] lei refresh-mail-sync
Date: Thu, 16 Sep 2021 09:41:13 +0000	[thread overview]
Message-ID: <20210916094116.11457-1-e@80x24.org> (raw)

The command I need because lei-daemon keeps dying so inotify
ain't useful :P  Well, actually, I just restart lei-daemon
frequently because I'm always changing code.

1/3 is a nice cleanup, 2/3 makes the change

AFAIK, refresh-mail-sync (and prune-mail-sync before it)
were the only which could trigger the bug fixed in PATCH 3/3

Eric Wong (3):
  lei: git_oid: replace git_blob_id
  lei refresh-mail-sync: replace prune-mail-sync
  net_reader: ensure IO::Socket::Socks is loaded in all workers

 MANIFEST                                      |  2 +
 lib/PublicInbox/LEI.pm                        | 13 ++--
 lib/PublicInbox/LeiInspect.pm                 |  3 +-
 ...PruneMailSync.pm => LeiRefreshMailSync.pm} | 36 +++++++---
 lib/PublicInbox/LeiRemote.pm                  |  2 +-
 lib/PublicInbox/LeiStore.pm                   | 14 ++--
 lib/PublicInbox/LeiXSearch.pm                 |  3 +-
 lib/PublicInbox/NetReader.pm                  |  5 ++
 t/lei-export-kw.t                             |  1 -
 t/lei-refresh-mail-sync.t                     | 67 +++++++++++++++++++
 10 files changed, 121 insertions(+), 25 deletions(-)
 rename lib/PublicInbox/{LeiPruneMailSync.pm => LeiRefreshMailSync.pm} (70%)
 create mode 100644 t/lei-refresh-mail-sync.t


             reply	other threads:[~2021-09-16  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  9:41 Eric Wong [this message]
2021-09-16  9:41 ` [PATCH 1/3] lei: git_oid: replace git_blob_id Eric Wong
2021-09-16  9:41 ` [PATCH 2/3] lei refresh-mail-sync: replace prune-mail-sync Eric Wong
2021-09-16  9:46   ` [SQUASH] fix manifest Eric Wong
2021-09-16  9:41 ` [PATCH 3/3] net_reader: load IO::Socket::Socks in all workers 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=20210916094116.11457-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).