From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [BUGFIX] rust-sccache: update to 0.2.15, enable feature=dist-server for x86_64*
Date: Sun, 29 May 2022 04:13:44 +0200 [thread overview]
Message-ID: <20220529021344.BGm0MZ0AkRwe4De74r1MKqpF8M-sZY5KL0Eu1xavGCo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29756@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
There's a closed pull request on the void-packages repository
[BUGFIX] rust-sccache: update to 0.2.15, enable feature=dist-server for x86_64*
https://github.com/void-linux/void-packages/pull/29756
Description:
<!-- Mark items with [x] where applicable -->
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
prev parent reply other threads:[~2022-05-29 2:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 20:22 [PR PATCH] rust-sccache: update to 0.2.15 Logarithmus
2021-03-25 20:28 ` ericonr
2021-03-26 10:10 ` [PR PATCH] [Updated] " Logarithmus
2021-03-26 21:28 ` Logarithmus
2021-03-26 21:32 ` Logarithmus
2021-03-26 21:33 ` Logarithmus
2021-03-26 21:41 ` [PR PATCH] [Updated] rust-sccache: update to 0.2.15, enable dist-server feature Logarithmus
2021-03-27 13:28 ` Logarithmus
2021-03-27 15:05 ` Logarithmus
2021-03-27 15:06 ` Logarithmus
2021-03-27 15:08 ` rust-sccache: update to 0.2.15, new package: rust-sccache-dist-0.2.15 Logarithmus
2021-03-27 15:09 ` [PR PATCH] [Updated] " Logarithmus
2021-03-27 15:10 ` Logarithmus
2021-03-27 19:14 ` Logarithmus
2021-03-27 19:16 ` [PR PATCH] [Updated] " Logarithmus
2021-04-01 17:33 ` Logarithmus
2021-04-01 17:34 ` Logarithmus
2021-05-05 13:36 ` Logarithmus
2021-05-05 13:39 ` Logarithmus
2021-05-05 20:16 ` Logarithmus
2021-05-06 8:20 ` [BUGFIX] " Logarithmus
2021-05-06 9:36 ` Logarithmus
2021-05-06 14:54 ` ericonr
2021-06-29 11:59 ` [PR PATCH] [Updated] " Logarithmus
2021-06-29 12:03 ` Logarithmus
2021-06-29 21:52 ` Logarithmus
2021-06-29 22:08 ` Logarithmus
2021-07-01 12:26 ` [PR PATCH] [Updated] [BUGFIX] rust-sccache: update to 0.2.15, enable feature=dist-server for x86_64* Logarithmus
2021-07-18 14:51 ` Logarithmus
2021-07-27 1:06 ` Logarithmus
2021-07-27 1:08 ` Logarithmus
2021-07-27 1:10 ` Logarithmus
2021-07-27 1:51 ` Logarithmus
2021-07-27 1:56 ` Logarithmus
2021-07-27 6:23 ` redasamik
2022-05-14 2:17 ` github-actions
2022-05-29 2:13 ` github-actions [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=20220529021344.BGm0MZ0AkRwe4De74r1MKqpF8M-sZY5KL0Eu1xavGCo@z \
--to=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).