Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: rset-2.4
Date: Wed, 07 Sep 2022 04:15:28 +0200	[thread overview]
Message-ID: <20220907021528.XyrkUIgVp0DC0oYpX9yplW4SMj69jxhRhuRkL1e8YpM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31003@inbox.vuxu.org>

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

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

New package: rset-2.4
https://github.com/void-linux/void-packages/pull/31003

Description:
<!-- Mark items with [x] where applicable -->

#### General
- [x] 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] 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? 

- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-musl (cross)
  - [x] armv7l (cross)
  - [x] armv6l-musl (cross)

      parent reply	other threads:[~2022-09-07  2:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  1:20 [PR PATCH] New package: rset-2.1 Benjamin-L
2021-05-21  1:40 ` [PR PATCH] [Updated] " Benjamin-L
2021-05-21  1:40 ` Benjamin-L
2021-05-21  5:46 ` Benjamin-L
2021-05-22  8:23 ` Benjamin-L
2021-05-22  8:29 ` [PR PATCH] [Updated] " Benjamin-L
2021-05-22 16:02 ` [PR REVIEW] " eradman
2021-05-22 19:27 ` [PR PATCH] [Updated] " Benjamin-L
2021-05-22 19:27 ` [PR REVIEW] " Benjamin-L
2021-05-29  4:41 ` Benjamin-L
2022-05-20  2:12 ` github-actions
2022-05-23 22:02 ` Benjamin-L
2022-05-23 22:17 ` [PR PATCH] [Updated] New package: rset-2.4 Benjamin-L
2022-05-24  4:32 ` Benjamin-L
2022-05-24 20:05 ` Benjamin-L
2022-05-24 20:08 ` Benjamin-L
2022-05-25  2:15 ` [PR PATCH] [Updated] " Benjamin-L
2022-08-24  2:14 ` github-actions
2022-09-07  2:15 ` github-actions [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=20220907021528.XyrkUIgVp0DC0oYpX9yplW4SMj69jxhRhuRkL1e8YpM@z \
    --to=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).