Github messages for voidlinux
 help / color / mirror / Atom feed
From: r-ricci <r-ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: v4l-utils: merge with qv4l2, add qvidcap subpackage
Date: Fri, 05 Aug 2022 22:41:25 +0200	[thread overview]
Message-ID: <20220805204125.Yjx1yBXtMs2fRzgCbZC0bEw7lAT03308ScptZL9TCWA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36845@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

There's a closed pull request on the void-packages repository

v4l-utils: merge with qv4l2, add qvidcap subpackage
https://github.com/void-linux/void-packages/pull/36845

Description:
- remove patches, since they are already upstream
- clean up template

`qvidcap` was not built in the `v4l-utils` template and not installed in the `qv4l2` template. Some of its functionality overlaps with `qv4l2`, I don't know if it's actually useful to package.

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


      parent reply	other threads:[~2022-08-05 20:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  2:41 [PR PATCH] " 4ricci
2022-07-25  2:14 ` github-actions
2022-08-05 14:03 ` [PR PATCH] [Updated] " r-ricci
2022-08-05 15:10 ` q66
2022-08-05 20:41 ` r-ricci [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=20220805204125.Yjx1yBXtMs2fRzgCbZC0bEw7lAT03308ScptZL9TCWA@z \
    --to=r-ricci@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).