From: jbruchon <jbruchon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: jdupes: update to 1.23.0, adopt; New package: libjodycode-2.0
Date: Wed, 10 May 2023 05:32:59 +0200 [thread overview]
Message-ID: <20230510033259.z9bLLbcDH5XMKebl31-DkHUYjEsQvLWbS3nUCnNdosU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43425@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
New comment by jbruchon on void-packages repository
https://github.com/void-linux/void-packages/pull/43425#issuecomment-1541298986
Comment:
Hey! I'm actually a Void user and noticed the repo was behind and discovered this. In libjodycode I changed the Makefile to fix this: https://github.com/jbruchon/libjodycode/commit/0a99bf3442fd509e77d7ea52e08efc9e202e44b0 - Thanks for finding this problem!
next prev parent reply other threads:[~2023-05-10 3:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 13:46 [PR PATCH] jdupes: update to 1.22.0, adopt; New package: libjodycode-1.0 cinerea0
2023-04-21 2:05 ` [PR PATCH] [Updated] " cinerea0
2023-04-21 2:10 ` [PR PATCH] [Updated] jdupes: update to 1.22.0, adopt; New package: libjodycode-1.1 cinerea0
2023-04-25 14:48 ` cinerea0
2023-04-25 19:52 ` [PR PATCH] [Updated] jdupes: update to 1.22.0, adopt; New package: libjodycode-1.2 cinerea0
2023-04-26 15:01 ` cinerea0
2023-05-10 2:13 ` cinerea0
2023-05-10 3:32 ` jbruchon [this message]
2023-05-10 13:47 ` jdupes: update to 1.23.0, adopt; New package: libjodycode-2.0 leahneukirchen
2023-05-10 15:01 ` jbruchon
2023-05-10 15:48 ` leahneukirchen
2023-05-10 15:56 ` jbruchon
2023-05-10 15:56 ` jbruchon
2023-05-17 3:30 ` [PR PATCH] [Updated] " cinerea0
2023-05-17 11:34 ` [PR PATCH] [Merged]: jdupes: update to 1.23.0, adopt; New package: libjodycode-2.0.1 leahneukirchen
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=20230510033259.z9bLLbcDH5XMKebl31-DkHUYjEsQvLWbS3nUCnNdosU@z \
--to=jbruchon@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).