From: Vulldozer <Vulldozer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: wlrobs-1.1
Date: Sun, 13 Nov 2022 12:40:41 +0100 [thread overview]
Message-ID: <20221113114041._oR1DI3mEzljPjQgR_c_PW9f4-d2dlW5SSCTCdiCnvQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40501@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
There is an updated pull request by Vulldozer against master on the void-packages repository
https://github.com/Vulldozer/void-packages add-wlrobs
https://github.com/void-linux/void-packages/pull/40501
New package: wlrobs-1.1
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
This template packages version 1.1 of wlrobs and addresses the issues in #29773
> What's the difference between this plugin and a proper setup with pipewire and portals?
The output you choose to capture and the crop/scale will be remembered, no need to use a tool to pick which display to capture every time, which allows smoother transitions between scenes.
A patch file from https://github.com/void-linux/void-packages/pull/40501.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-add-wlrobs-40501.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]
next prev parent reply other threads:[~2022-11-13 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 10:53 [PR PATCH] " Vulldozer
2022-11-13 11:25 ` [PR PATCH] [Updated] " Vulldozer
2022-11-13 11:39 ` Vulldozer
2022-11-13 11:40 ` [PR PATCH] [Closed]: " Vulldozer
2022-11-13 11:40 ` Vulldozer [this message]
2022-11-13 12:07 [PR PATCH] " Vulldozer
2022-12-21 19:59 ` [PR PATCH] [Updated] " Vulldozer
2022-12-26 20:05 ` Vulldozer
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=20221113114041._oR1DI3mEzljPjQgR_c_PW9f4-d2dlW5SSCTCdiCnvQ@z \
--to=vulldozer@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).