From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Update template
Date: Thu, 13 Jan 2022 09:13:15 +0100 [thread overview]
Message-ID: <20220113081315.4jAKnABGdPbpu0d95CNWg0z7KLEyhG_VRwvK7THbYto@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34519@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
There's a closed pull request on the void-packages repository
Update template
https://github.com/void-linux/void-packages/pull/34519
Description:
<!-- 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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 glibc)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
## Trying again
pull request #33537
next prev parent reply other threads:[~2022-01-13 8:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 1:28 [PR PATCH] " zen0bit
2021-12-14 13:19 ` Duncaen
2022-01-12 17:55 ` [PR PATCH] [Updated] " zen0bit
2022-01-12 17:59 ` zen0bit
2022-01-12 19:03 ` [PR REVIEW] " paper42
2022-01-12 19:05 ` [PR PATCH] [Updated] " zen0bit
2022-01-13 6:42 ` zen0bit
2022-01-13 6:45 ` zen0bit
2022-01-13 7:06 ` zen0bit
2022-01-13 7:16 ` zen0bit
2022-01-13 7:20 ` zen0bit
2022-01-13 7:43 ` zen0bit
2022-01-13 7:44 ` [PR REVIEW] " zen0bit
2022-01-13 8:13 ` zen0bit [this message]
2022-01-14 12:19 ` paper42
2022-01-14 18:48 ` zen0bit
2022-01-14 18:59 ` [PR PATCH] [Updated] " zen0bit
2022-01-14 22:05 ` paper42
2022-01-30 15:24 ` [PR PATCH] [Updated] " zen0bit
2022-01-30 15:26 ` zen0bit
2022-01-30 17:02 ` [PR PATCH] [Closed]: " paper42
2022-01-30 17:02 ` paper42
2022-01-30 17:41 ` zen0bit
2022-01-30 17:41 ` paper42
-- strict thread matches above, loose matches on Subject: below --
2021-04-28 22:08 [PR PATCH] " grim-cypher
2021-05-17 3:57 ` [PR PATCH] [Closed]: " ericonr
2020-09-11 21:57 [PR PATCH] " the-cleaner-66
2020-09-12 8:08 ` [PR PATCH] [Closed]: " pullmoll
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20133@inbox.vuxu.org>
2020-03-16 14:32 ` nasipkalid
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=20220113081315.4jAKnABGdPbpu0d95CNWg0z7KLEyhG_VRwvK7THbYto@z \
--to=zen0bit@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).