From: ebiederm@xmission.com (Eric W. Biederman)
To: Eric Wong <e@80x24.org>
Cc: <meta@public-inbox.org>
Subject: Q: Did you do something to message number recently?
Date: Mon, 24 Jun 2019 10:59:08 -0500 [thread overview]
Message-ID: <878strvusz.fsf@xmission.com> (raw)
Eric,
I am just starting to dig into this, I just noticed that I have several
inboxes that are seeing huge skips in message numbers assigned in
msgmap. Do you have any idea why this would be?
If not I will dig in and figure this out. I just figured I would ask
in case you have any handy canidates.
I thought I had a regression test in public-inbox to catch this.
Eric
next reply other threads:[~2019-06-24 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 15:59 Eric W. Biederman [this message]
2019-06-24 16:34 ` Q: Did you do something to message number recently? Eric Wong
2019-06-24 17:33 ` Eric Wong
2019-06-24 22:56 ` Eric W. Biederman
2019-06-24 23:42 ` Eric Wong
2019-06-25 12:01 ` Eric W. Biederman
2019-06-25 17:51 ` Eric Wong
2019-06-24 23:38 ` [PATCH] msgmap: mid_insert: use plain "INSERT" to detect duplicates Eric Wong
2019-06-25 3:48 ` 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=878strvusz.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=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.
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).