From: ahesford <email@example.com> To: firstname.lastname@example.org Subject: Re: [PR PATCH] [Closed]: crun: update to 1.2. Date: Thu, 14 Oct 2021 19:14:59 +0200 [thread overview] Message-ID: <20211014171459.JabNUJ5wSS1AKK6NrmpbJITcaQGuHmSBm-npPC-uakg@z> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1431 bytes --] There's a closed pull request on the void-packages repository crun: update to 1.2. https://github.com/void-linux/void-packages/pull/33520 Description: <!-- Mark items with [x] where applicable --> #### General - [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements) #### 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:[~2021-10-14 17:14 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-13 12:03 [PR PATCH] " natrys 2021-10-14 17:14 ` ahesford [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=20211014171459.JabNUJ5wSS1AKK6NrmpbJITcaQGuHmSBm-npPC-uakg@z \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PR PATCH] [Closed]: crun: update to 1.2.' \ /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
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).