From: hiljusti <hiljusti@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: sigi-3.1.0
Date: Sat, 02 Apr 2022 21:49:07 +0200 [thread overview]
Message-ID: <20220402194907.KQz3I5kh0GbWxezRWxiHec5IsC5Rvm9YMT8K98RgTzA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29907@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
New review comment by hiljusti on void-packages repository
https://github.com/void-linux/void-packages/pull/29907#discussion_r841112744
Comment:
I'll update the homepage, but right now I want to keep the distfile at crates.io. The link is immutable, and publishing to crates.io has some really basic validation, like the sources being compilable
next prev parent reply other threads:[~2022-04-02 19:49 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 9:57 [PR PATCH] New package: sigi-0.2.0 hiljusti
2021-03-31 11:13 ` New package: sigi-0.2.1 ericonr
2021-03-31 16:03 ` [PR PATCH] [Updated] " hiljusti
2021-03-31 16:04 ` hiljusti
2021-04-02 19:06 ` [PR PATCH] [Updated] " hiljusti
2021-04-03 3:32 ` hiljusti
2021-04-03 4:17 ` [PR PATCH] [Updated] " hiljusti
2021-04-08 0:28 ` [PR PATCH] [Updated] New package: sigi-0.2.2 hiljusti
2021-04-15 4:37 ` New package: sigi-0.2.3 cinerea0
2021-04-15 4:38 ` cinerea0
2021-04-15 5:00 ` [PR PATCH] [Updated] " hiljusti
2021-04-15 5:02 ` [PR PATCH] [Updated] New package: sigi-0.2.4 hiljusti
2021-04-15 5:03 ` hiljusti
2021-04-17 6:19 ` ericonr
2021-04-21 3:04 ` hiljusti
2021-04-21 3:17 ` hiljusti
2021-04-21 9:52 ` [PR PATCH] [Updated] " hiljusti
2021-04-29 6:29 ` [PR PATCH] [Updated] New package: sigi-0.2.5 hiljusti
2021-06-24 5:10 ` [PR PATCH] [Updated] New package: sigi-0.2.7 hiljusti
2021-07-05 23:46 ` hiljusti
2021-07-12 19:44 ` [PR PATCH] [Updated] New package: sigi-1.0.1 hiljusti
2021-11-26 18:44 ` [PR PATCH] [Updated] New package: sigi-1.1.0 hiljusti
2021-11-26 18:44 ` [PR PATCH] [Closed]: " hiljusti
2021-11-26 19:26 ` [PR PATCH] [Updated] New package: sigi-2.0.1 hiljusti
2021-11-26 19:39 ` hiljusti
2021-11-26 19:39 ` hiljusti
2021-11-26 19:40 ` hiljusti
2021-11-29 1:38 ` [PR PATCH] [Updated] " hiljusti
2021-11-29 1:39 ` hiljusti
2021-11-29 5:55 ` [PR PATCH] [Updated] " hiljusti
2021-11-30 18:38 ` hiljusti
2021-11-30 21:35 ` hiljusti
2021-12-08 0:42 ` New package: sigi-2.1.1 hiljusti
2021-12-11 2:39 ` ericonr
2021-12-12 8:58 ` [PR PATCH] [Updated] " hiljusti
2021-12-12 8:59 ` hiljusti
2021-12-13 17:30 ` [PR PATCH] [Updated] " hiljusti
2021-12-13 17:30 ` hiljusti
2021-12-17 19:22 ` hiljusti
2022-01-08 6:05 ` hiljusti
2022-01-12 9:49 ` [PR PATCH] [Updated] " hiljusti
2022-01-12 9:50 ` New package: sigi-3.0.0 hiljusti
2022-01-12 9:54 ` hiljusti
2022-01-12 9:58 ` [PR PATCH] [Updated] " hiljusti
2022-02-02 10:28 ` hiljusti
2022-02-02 10:29 ` hiljusti
2022-02-02 10:33 ` [PR PATCH] [Updated] " hiljusti
2022-03-09 9:17 ` hiljusti
2022-03-09 9:18 ` New package: sigi-3.0.1 hiljusti
2022-03-09 9:18 ` hiljusti
2022-03-09 10:05 ` [PR PATCH] [Updated] " hiljusti
2022-03-09 10:05 ` hiljusti
2022-03-09 10:14 ` [PR PATCH] [Updated] New package: sigi-3.0.2 hiljusti
2022-03-19 8:47 ` hiljusti
2022-03-19 8:49 ` [PR PATCH] [Updated] New package: sigi-3.0.3 hiljusti
2022-03-22 6:26 ` hiljusti
2022-03-28 8:01 ` [PR PATCH] [Updated] " hiljusti
2022-03-28 8:02 ` hiljusti
2022-04-01 8:04 ` [PR PATCH] [Updated] New package: sigi-3.1.0 hiljusti
2022-04-01 8:07 ` hiljusti
2022-04-01 11:49 ` [PR REVIEW] " subnut
2022-04-01 11:49 ` subnut
2022-04-02 19:26 ` hiljusti
2022-04-02 19:26 ` hiljusti
2022-04-02 19:28 ` hiljusti
2022-04-02 19:29 ` hiljusti
2022-04-02 19:34 ` [PR PATCH] [Updated] " hiljusti
2022-04-02 19:35 ` [PR REVIEW] " hiljusti
2022-04-02 19:46 ` [PR PATCH] [Updated] " hiljusti
2022-04-02 19:49 ` hiljusti [this message]
2022-04-03 5:44 ` hiljusti
2022-04-07 4:17 ` [PR PATCH] [Merged]: " the-maldridge
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=20220402194907.KQz3I5kh0GbWxezRWxiHec5IsC5Rvm9YMT8K98RgTzA@z \
--to=hiljusti@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).