From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: brightnessctl: added elogind build option
Date: Mon, 13 Feb 2023 03:01:41 +0100 [thread overview]
Message-ID: <20230213020141.QChFv3ebTEqjUNN-slflHD-bMxNFL2fu9HuQyMqktiY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38338@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
There's a closed pull request on the void-packages repository
brightnessctl: added elogind build option
https://github.com/void-linux/void-packages/pull/38338
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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, (amd64-glibc)
This option allows brightnessctl to access backlight devices using the `(e)logind` api. First PR, and I wasn't sure if a revbump was necessary. If I need to change anything lmk.
prev parent reply other threads:[~2023-02-13 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 16:11 [PR PATCH] " epixtm
2022-10-27 2:13 ` github-actions
2022-10-30 23:37 ` epixtm
2023-01-30 1:57 ` github-actions
2023-02-13 2:01 ` 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=20230213020141.QChFv3ebTEqjUNN-slflHD-bMxNFL2fu9HuQyMqktiY@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).