From: michalszmidt <michalszmidt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: hctl-0.2.2.1
Date: Wed, 06 Sep 2023 02:40:38 +0200 [thread overview]
Message-ID: <20230906004038.9zg54q6uiHUtKJVXYxuegf4VIOdmIqSjM14YABGlAOI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45905@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
New review comment by michalszmidt on void-packages repository
https://github.com/void-linux/void-packages/pull/45905#discussion_r1316530474
Comment:
Right, it passes without `depends=openssl`
One more thing. Alpine Maintainers [protested against](https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/51062#note_335395) the [BSD-3-Clause-**No-Military**](https://spdx.org/licenses/BSD-3-Clause-No-Military-License.html) so I must have changed it to just [BSD-3-Clause](https://spdx.org/licenses/BSD-3-Clause.html). I rebased amended and force pushed [code for 0.2.2 commit](https://github.com/michalszmidt/hctl/commit/7897bd115bf279c08b0971509006afc375dd6fae) adding new license there but old archive is glued to release. So i made a new tag 0.2.2.1 with modified license.
So next force push contains also License change and checksum update.
Also `revision=0`as this new package.
EDIT:
Actually, on void it should be `revision=1` else xlint fails.
next prev parent reply other threads:[~2023-09-06 0:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 14:20 [PR PATCH] New package: hctl-0.2.2 michalszmidt
2023-09-05 17:51 ` classabbyamp
2023-09-05 18:36 ` michalszmidt
2023-09-05 18:48 ` [PR REVIEW] " classabbyamp
2023-09-05 18:48 ` classabbyamp
2023-09-05 18:48 ` classabbyamp
2023-09-05 18:48 ` classabbyamp
2023-09-05 18:48 ` classabbyamp
2023-09-05 19:09 ` [PR PATCH] [Updated] " michalszmidt
2023-09-05 19:15 ` michalszmidt
2023-09-05 19:16 ` michalszmidt
2023-09-05 19:29 ` [PR REVIEW] " classabbyamp
2023-09-05 20:18 ` michalszmidt
2023-09-05 20:19 ` classabbyamp
2023-09-05 23:57 ` [PR PATCH] [Updated] " michalszmidt
2023-09-05 23:57 ` [PR REVIEW] " michalszmidt
2023-09-06 0:39 ` [PR PATCH] [Updated] New package: hctl-0.2.2.1 michalszmidt
2023-09-06 0:40 ` michalszmidt [this message]
2023-09-07 12:11 ` michalszmidt
2023-10-14 11:55 ` [PR PATCH] [Updated] " michalszmidt
2023-10-14 11:56 ` New package: hctl-0.2.4 michalszmidt
2023-10-14 12:00 ` [PR PATCH] [Updated] " michalszmidt
2023-12-06 13:47 ` michalszmidt
2023-12-06 14:39 ` michalszmidt
2023-12-06 14:40 ` michalszmidt
2024-02-13 16:21 ` New package: hctl-0.2.5 melroy89
2024-03-04 20:42 ` [PR PATCH] [Updated] " michalszmidt
2024-03-04 21:03 ` michalszmidt
2024-03-04 21:05 ` New package: hctl-0.2.6 michalszmidt
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=20230906004038.9zg54q6uiHUtKJVXYxuegf4VIOdmIqSjM14YABGlAOI@z \
--to=michalszmidt@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).