From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New Package: hplip-plugin-3.22.10
Date: Wed, 16 Nov 2022 15:08:45 +0100 [thread overview]
Message-ID: <20221116140845.oSENFci2Wm3ui-QID4HTkpGnGQjFxBBv7VsN0n7-Nb4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39147@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
There's a closed pull request on the void-packages repository
New Package: hplip-plugin-3.22.10
https://github.com/void-linux/void-packages/pull/39147
Description:
I've got asked by @biopsin to fix his PR #37287.
The corresponding `hplip` PR is #39146.
I've changed some things in the template to standardize it.
---
**The package is restricted.**
#### Testing the changes
- I tested the changes in this PR: **YES - tested by @biopsin**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- i686 (crossbuild)
- aarch64 (crossbuild)
- armv7l (crossbuild)
- armv6l (crossbuild)
next prev parent reply other threads:[~2022-11-16 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 9:08 [PR PATCH] New Package: hplip-plugin-3.22.6 dataCobra
2022-09-07 9:08 ` [PR PATCH] [Updated] " dataCobra
2022-09-14 4:52 ` dataCobra
2022-10-15 8:01 ` dataCobra
2022-11-04 6:27 ` dataCobra
2022-11-10 5:54 ` dataCobra
2022-11-10 5:57 ` dataCobra
2022-11-16 13:36 ` New Package: hplip-plugin-3.22.10 dataCobra
2022-11-16 14:08 ` dataCobra
2022-11-16 14:08 ` dataCobra [this message]
2022-11-16 14:11 ` [PR REVIEW] " sgn
2022-11-16 14:11 ` sgn
2022-11-16 14:19 ` dataCobra
2022-11-16 14:25 ` dataCobra
2022-11-16 14:30 ` sgn
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=20221116140845.oSENFci2Wm3ui-QID4HTkpGnGQjFxBBv7VsN0n7-Nb4@z \
--to=datacobra@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).