From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New Package: clickclack-0.2.2
Date: Wed, 11 May 2022 00:30:44 +0200 [thread overview]
Message-ID: <20220510223044.8UjX2hw61KTgJ_K4NAucA8587n5TZyGQqFRfjiMNE9k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36915@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
New review comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/36915#discussion_r869727196
Comment:
`0.2.3` has now been tagged and includes the fixes from my previously mentioned patch series including the cross-compile patch, so that can be dropped as well after updating :)
Btw it appears `./xbps-src update-check clickclack` fails to find an upstream version currently, so adding an `update` file [as per the XBPS source packages manual](https://github.com/void-linux/void-packages/blob/master/Manual.md#checking-for-new-upstream-releases) with `pattern='\s{12}\K[\d.]+'` in it should fix this (for now at least).
next prev parent reply other threads:[~2022-05-10 22:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 20:22 [PR PATCH] " Eloitor
2022-04-29 20:25 ` [PR PATCH] [Updated] " Eloitor
2022-05-09 16:01 ` [PR REVIEW] " JamiKettunen
2022-05-09 16:02 ` JamiKettunen
2022-05-09 16:34 ` [PR PATCH] [Updated] " Eloitor
2022-05-09 16:48 ` Eloitor
2022-05-09 20:20 ` Eloitor
2022-05-09 20:20 ` Eloitor
2022-05-09 21:52 ` [PR REVIEW] " paper42
2022-05-09 21:52 ` paper42
2022-05-09 21:52 ` paper42
2022-05-10 11:10 ` JamiKettunen
2022-05-10 11:11 ` JamiKettunen
2022-05-10 12:27 ` JamiKettunen
2022-05-10 20:54 ` [PR PATCH] [Updated] " Eloitor
2022-05-10 20:54 ` [PR REVIEW] " Eloitor
2022-05-10 22:30 ` JamiKettunen [this message]
2022-05-12 8:12 ` [PR PATCH] [Updated] " Eloitor
2022-05-12 8:14 ` Eloitor
2022-05-13 19:18 ` [PR PATCH] [Merged]: New Package: clickclack-0.2.3 paper42
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=20220510223044.8UjX2hw61KTgJ_K4NAucA8587n5TZyGQqFRfjiMNE9k@z \
--to=jamikettunen@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).