From: bertronika <bertronika@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: uthash: update to 2.3.0.
Date: Sat, 02 Oct 2021 17:54:23 +0200 [thread overview]
Message-ID: <20211002155423.8chrdA4TLiW5iIzk0GMXI1JeT6Z-fQjA5ijTOppSSHo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33265@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
New comment by bertronika on void-packages repository
https://github.com/void-linux/void-packages/pull/33265#issuecomment-932774326
Comment:
I've amended the commit - added upstream changelog, fixed short description.
Regarding uthash deprecating functions: following seems to have been removed since 2.1.0:
- `HASH_FCN`
- `uthash_memcmp`
- `HASH_MUR`
- `oom` separated to `utarray_oom` and `utstring_oom`
I've checked upstream repos for the following packages, gathered with `grep -rli utash` in void-packages/srcpkgs:
- alttab
- picom
- xcb-imdkit
- burp2-server
- rmilter
- logtop
- mle
- mhddfs
- mosquitto
There were also a couple of patches:
- wordgrinder/patches/fix-xft-include.patch
- rmilter/patches/de-vendor.patch
As far as I can tell, none of the packages and patches are using the deprecated functions. Only occurrences of them were in `uthash.h` and other `ut*.h` files, included upstream, meaning those packages don't even depend on Void's version.
next prev parent reply other threads:[~2021-10-02 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 13:50 [PR PATCH] " bertronika
2021-10-02 14:45 ` Chocimier
2021-10-02 15:48 ` [PR PATCH] [Updated] " bertronika
2021-10-02 15:54 ` bertronika [this message]
2021-10-25 20:32 ` Piraty
2021-10-25 20:34 ` [PR PATCH] [Closed]: " Piraty
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211002155423.8chrdA4TLiW5iIzk0GMXI1JeT6Z-fQjA5ijTOppSSHo@z \
--to=bertronika@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).