From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: aws-cli: update to 1.22.23 (with deps)
Date: Mon, 13 Dec 2021 00:45:14 +0100 [thread overview]
Message-ID: <20211212234514.KlxaqH4h09jL1LScsgJk7iHqsf3Jp6VerhAJEBzCl-g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34490@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
There's a merged pull request on the void-packages repository
aws-cli: update to 1.22.23 (with deps)
https://github.com/void-linux/void-packages/pull/34490
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: yes
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
prev parent reply other threads:[~2021-12-12 23:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 3:35 [PR PATCH] Aws 2112 bobertlo
2021-12-12 5:17 ` aws-cli: update to 1.22.23 (with deps) uhohspaghetios
2021-12-12 8:43 ` dotnetfox
2021-12-12 11:33 ` paper42
2021-12-12 12:49 ` bobertlo
2021-12-12 13:44 ` paper42
2021-12-12 13:46 ` paper42
2021-12-12 13:54 ` paper42
2021-12-12 13:54 ` paper42
2021-12-12 18:02 ` [PR PATCH] [Updated] " bobertlo
2021-12-12 18:08 ` bobertlo
2021-12-12 20:50 ` [PR REVIEW] " paper42
2021-12-12 20:50 ` paper42
2021-12-12 20:50 ` paper42
2021-12-12 23:14 ` [PR PATCH] [Updated] " bobertlo
2021-12-12 23:21 ` bobertlo
2021-12-12 23:45 ` paper42 [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=20211212234514.KlxaqH4h09jL1LScsgJk7iHqsf3Jp6VerhAJEBzCl-g@z \
--to=paper42@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).