From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PUSHED] fix reindex on multiple + overlapping Message-IDs
Date: Wed, 23 Oct 2019 18:19:29 +0000 [thread overview]
Message-ID: <20191023181929.GA15022@dcvr> (raw)
In-Reply-To: <20191021110221.23753-1-e@80x24.org>
Eric Wong <e@80x24.org> wrote:
> I'm still testing this with various repos, but the
> linux-renesas-soc mirror from lore seems good when doing initial
> indexing with an old version of this and using --reindex with
> this patch, as all previously-missed messages are now indexed.
Seems fine and pushed all 5 patches. However, display issues
still need to be fixed in the HTML...
> Eric Wong (3):
> v2writable: set unindexed article number
> v2writable: improve "num_for" API and disambiguate
> v2writable: reindex handles 3-headered monsters
v2writable: move git->cleanup to the correct place
v2writable: use msgmap as multi_mid queue
prev parent reply other threads:[~2019-10-23 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 21:14 BUG: --reindex broken on multiple Message-IDs reuse Eric Wong
2019-10-17 11:22 ` [RFC] v2writable: reindex handles 3-headed monsters [was: BUG: --reindex broken on multiple Message-IDs reuse] Eric Wong
2019-10-22 8:09 ` [RFC/HELP] search: multiple From/To/Cc/Subject (what about Date?) Eric Wong
2019-10-21 11:02 ` [PATCH 0/3] fix reindex on multiple + overlapping Message-IDs Eric Wong
2019-10-21 11:02 ` [PATCH 1/3] v2writable: set unindexed article number Eric Wong
2019-10-21 11:02 ` [PATCH 2/3] v2writable: improve "num_for" API and disambiguate Eric Wong
2019-10-21 11:02 ` [PATCH 3/3] v2writable: reindex handles 3-headered monsters Eric Wong
2019-10-21 11:34 ` Eric Wong
2019-10-22 1:28 ` [PATCH 4/3] v2writable: move git->cleanup to the correct place Eric Wong
2019-10-22 1:29 ` [PATCH 5/3] v2writable: use msgmap as multi_mid queue Eric Wong
2019-10-23 18:19 ` Eric Wong [this message]
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=20191023181929.GA15022@dcvr \
--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).