From: wibed <wibed@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: libcgroup: update to 2.0.
Date: Sun, 22 Aug 2021 06:07:36 +0200 [thread overview]
Message-ID: <20210822040736.UkxicCHDA1RPM3AJoJmSUWfqKGPh89Ml8gBtvmwaSgY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32231@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
There's a closed pull request on the void-packages repository
libcgroup: update to 2.0.
https://github.com/void-linux/void-packages/pull/32231
Description:
update libcgroup to version 2.0
<!-- 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] 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.)
- [x] I built this PR locally for my native architecture, (x86_64-musl)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
next prev parent reply other threads:[~2021-08-22 4:07 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 15:54 [PR PATCH] " wibed
2021-07-28 15:59 ` [PR REVIEW] " paper42
2021-07-28 15:59 ` paper42
2021-07-28 15:59 ` paper42
2021-07-28 15:59 ` paper42
2021-07-28 16:01 ` paper42
2021-07-28 16:15 ` [PR PATCH] [Updated] " wibed
2021-07-28 16:16 ` [PR REVIEW] " wibed
2021-07-28 16:17 ` wibed
2021-07-28 16:17 ` paper42
2021-07-28 16:17 ` paper42
2021-07-28 16:17 ` wibed
2021-07-28 16:17 ` wibed
2021-07-28 16:33 ` paper42
2021-07-28 16:37 ` wibed
2021-07-28 16:39 ` paper42
2021-07-28 16:40 ` paper42
2021-07-28 16:41 ` paper42
2021-07-28 16:44 ` [PR PATCH] [Updated] " wibed
2021-07-28 16:45 ` [PR REVIEW] " wibed
2021-07-28 16:46 ` [PR PATCH] [Updated] " wibed
2021-07-28 16:47 ` [PR REVIEW] " wibed
2021-07-28 16:47 ` [PR PATCH] [Updated] " wibed
2021-07-28 16:48 ` [PR REVIEW] " wibed
2021-07-28 16:49 ` wibed
2021-07-28 16:59 ` paper42
2021-07-28 17:03 ` wibed
2021-07-28 17:14 ` [PR PATCH] [Updated] " wibed
2021-07-28 20:29 ` paper42
2021-07-28 20:36 ` [PR REVIEW] " paper42
2021-08-04 20:26 ` paper42
2021-08-12 17:11 ` paper42
2021-08-13 7:36 ` wibed
2021-08-18 3:22 ` [PR PATCH] [Updated] " wibed
2021-08-18 3:31 ` wibed
2021-08-18 3:40 ` wibed
2021-08-18 8:45 ` wibed
2021-08-18 16:11 ` [PR REVIEW] " paper42
2021-08-18 16:11 ` paper42
2021-08-18 16:12 ` paper42
2021-08-18 16:13 ` paper42
2021-08-19 12:56 ` [PR PATCH] [Updated] " wibed
2021-08-19 21:18 ` [PR REVIEW] " paper42
2021-08-20 0:13 ` [PR PATCH] [Updated] " wibed
2021-08-20 0:56 ` wibed
2021-08-20 1:05 ` wibed
2021-08-20 1:07 ` wibed
2021-08-20 1:09 ` wibed
2021-08-20 1:09 ` wibed
2021-08-20 1:46 ` [PR PATCH] [Updated] " wibed
2021-08-20 1:57 ` wibed
2021-08-20 15:56 ` ericonr
2021-08-21 0:50 ` [PR PATCH] [Updated] " wibed
2021-08-21 1:11 ` wibed
2021-08-21 1:17 ` wibed
2021-08-21 1:18 ` wibed
2021-08-21 1:21 ` wibed
2021-08-21 1:33 ` wibed
2021-08-21 2:55 ` [PR PATCH] [Updated] " wibed
2021-08-21 2:57 ` wibed
2021-08-21 3:07 ` wibed
2021-08-22 4:03 ` [PR PATCH] [Updated] " wibed
2021-08-22 4:07 ` wibed
2021-08-22 4:07 ` wibed [this message]
2021-08-22 4:29 [PR PATCH] libcgroup upgrade " wibed
2022-06-17 2:13 ` [PR PATCH] [Closed]: libcgroup: update " github-actions
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=20210822040736.UkxicCHDA1RPM3AJoJmSUWfqKGPh89Ml8gBtvmwaSgY@z \
--to=wibed@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).