From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: bdfresize-1.5
Date: Fri, 24 Jun 2022 22:04:57 +0200 [thread overview]
Message-ID: <20220624200457.fddtnpFcxhi-A1A8aA6hPca70gNaI6lgEMTj0m8voQ4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35548@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
There's a merged pull request on the void-packages repository
New package: bdfresize-1.5
https://github.com/void-linux/void-packages/pull/35548
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- 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 [skip CI](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-MUSL-LIBC)
This is my first package, I don't really know what I'm doing! Worked on this for a few hours referencing other packages and copied patches from the AUR package, which i think were patched for debian years before? I feel like I'm nearing the limit to what I can learn about creating an xbps package on my own, so here's the PR. This can be closed if you folks feel like it, or any other reason, I don't know what to expect.
prev parent reply other threads:[~2022-06-24 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 6:24 [PR PATCH] [WIP] " amydotsh
2022-02-12 17:21 ` amydotsh
2022-02-12 23:45 ` [PR PATCH] [Updated] " amydotsh
2022-02-12 23:47 ` amydotsh
2022-02-12 23:47 ` amydotsh
2022-02-12 23:47 ` amydotsh
2022-02-12 23:52 ` amydotsh
2022-02-13 16:12 ` [PR PATCH] [Updated] " amydotsh
2022-02-13 16:14 ` amydotsh
2022-02-13 21:40 ` amydotsh
2022-02-13 21:57 ` amydotsh
2022-02-13 21:59 ` amydotsh
2022-06-23 2:15 ` github-actions
2022-06-24 20:04 ` leahneukirchen [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=20220624200457.fddtnpFcxhi-A1A8aA6hPca70gNaI6lgEMTj0m8voQ4@z \
--to=leahneukirchen@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).