From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: cargo-nextest-0.9.44
Date: Tue, 03 Jan 2023 14:29:11 +0100 [thread overview]
Message-ID: <20230103132911._QEJknlAbw4fBm4xt2kSAPoi6OolL_IsHlo3kqdy8RM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38224@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
New comment by tranzystorek-io on void-packages repository
https://github.com/void-linux/void-packages/pull/38224#issuecomment-1369770777
Comment:
I'm opting to close this, the changes seem to be to frequent, and as a development tool it's already well available and usable via `cargo install`.
prev parent reply other threads:[~2023-01-03 13:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 20:49 [PR PATCH] New package: cargo-nextest-0.9.28 tranzystorek-io
2022-07-23 21:24 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-24 23:15 ` tranzystorek-io
2022-07-26 4:18 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.29 tranzystorek-io
2022-07-26 4:19 ` tranzystorek-io
2022-07-26 11:30 ` New package: cargo-nextest-0.9.30 tranzystorek-io
2022-07-26 11:30 ` tranzystorek-io
2022-07-26 11:34 ` tranzystorek-io
2022-07-28 7:15 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-29 5:25 ` tranzystorek-io
2022-07-31 5:54 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.31 tranzystorek-io
2022-07-31 21:57 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.32 tranzystorek-io
2022-08-13 6:47 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.33 tranzystorek-io
2022-08-17 21:43 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.34 tranzystorek-io
2022-08-24 10:38 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.35 tranzystorek-io
2022-08-24 22:37 ` tranzystorek-io
2022-09-08 5:52 ` tranzystorek-io
2022-09-30 18:52 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.36 tranzystorek-io
2022-10-03 17:31 ` tranzystorek-io
2022-10-06 5:41 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.37 tranzystorek-io
2022-10-14 20:27 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.38 tranzystorek-io
2022-10-26 8:21 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.39 tranzystorek-io
2022-11-01 22:12 ` tranzystorek-io
2022-11-02 7:34 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.41 tranzystorek-io
2022-11-05 7:57 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.42 tranzystorek-io
2022-11-23 22:19 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.43 tranzystorek-io
2022-11-25 20:25 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.44 tranzystorek-io
2022-12-12 18:04 ` tranzystorek-io
2023-01-03 13:27 ` tranzystorek-io
2023-01-03 13:27 ` [PR PATCH] [Closed]: " tranzystorek-io
2023-01-03 13:29 ` tranzystorek-io [this message]
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=20230103132911._QEJknlAbw4fBm4xt2kSAPoi6OolL_IsHlo3kqdy8RM@z \
--to=tranzystorek-io@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).