From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/5] Dragonfly BSD support
Date: Fri, 6 Oct 2023 09:45:59 +0000 [thread overview]
Message-ID: <20231006094604.95809-1-e@80x24.org> (raw)
Got one tmpfs + EVFILT_VNODE bug fixed in Dragonfly in the
process. Dealing with hdestroy implementation differences
is really making me consider khash...
Also considering using sysdefs-list output via $Config{cc}
to support sendmsg/recvmsg without needing Inline::C. `cc'
seems pretty standard across all *BSDs.
Eric Wong (5):
kqnotify: drop EV_CLEAR (edge triggering)
xap_helper.h: strdup keys for DragonFlyBSD hdestroy(3)
devel/sysdefs-list: show more info regardless of OS
t/dir_idle: dump event list on failure
finalize DragonFlyBSD support
devel/sysdefs-list | 45 +++++++++++++++++------------------
install/os.perl | 7 +++---
lib/PublicInbox/Daemon.pm | 4 ++--
lib/PublicInbox/IPC.pm | 1 +
lib/PublicInbox/KQNotify.pm | 2 +-
lib/PublicInbox/MboxLock.pm | 10 +++++---
lib/PublicInbox/POP3D.pm | 4 ++--
lib/PublicInbox/TestCommon.pm | 19 +++++++++++++--
lib/PublicInbox/xap_helper.h | 13 ++++++++--
t/dir_idle.t | 8 ++++---
t/ds-kqxs.t | 5 ++--
t/kqnotify.t | 28 +++++++++++++++++++++-
t/pop3d-limit.t | 4 +---
t/pop3d.t | 6 ++---
t/search.t | 2 +-
xt/pop3d-mpop.t | 5 ++--
16 files changed, 108 insertions(+), 55 deletions(-)
next reply other threads:[~2023-10-06 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 9:45 Eric Wong [this message]
2023-10-06 9:46 ` [PATCH 1/5] kqnotify: drop EV_CLEAR (edge triggering) Eric Wong
2023-10-06 9:46 ` [PATCH 2/5] xap_helper.h: strdup keys for DragonFlyBSD hdestroy(3) Eric Wong
2023-10-06 9:46 ` [PATCH 3/5] devel/sysdefs-list: show more info regardless of OS Eric Wong
2023-10-06 9:46 ` [PATCH 4/5] t/dir_idle: dump event list on failure Eric Wong
2023-10-06 9:46 ` [PATCH 5/5] finalize DragonFlyBSD support 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: http://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=20231006094604.95809-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).