From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/2] sharedkv: cleanup + bugfixes
Date: Mon, 14 Feb 2022 05:37:23 +0000 [thread overview]
Message-ID: <20220214053725.1080495-1-e@80x24.org> (raw)
Well, working on another "canary" project helped me notice some
faults for this one.
Eric Wong (2):
sharedkv: remove unused subs
sharedkv: avoid ambiguity for numeric-like string keys
lib/PublicInbox/SharedKV.pm | 52 ++++++++++++++++---------------------
t/shared_kv.t | 16 ++++--------
2 files changed, 28 insertions(+), 40 deletions(-)
next reply other threads:[~2022-02-14 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 5:37 Eric Wong [this message]
2022-02-14 5:37 ` [PATCH 1/2] sharedkv: remove unused subs Eric Wong
2022-02-14 5:37 ` [PATCH 2/2] sharedkv: avoid ambiguity for numeric-like string keys 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=20220214053725.1080495-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).