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]: Subsurface
Date: Thu, 18 May 2023 03:52:57 +0200	[thread overview]
Message-ID: <20230518015257.nZtz_VUbEK2u4B08-e6dKpyl-E_bUym4PF0UND54LBE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34187@inbox.vuxu.org>

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

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

Subsurface
https://github.com/void-linux/void-packages/pull/34187

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, x86_64, x86_64-musl, i686
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64, aarch64-musl
 
I have been using subsurface for some time and have used on x86_64 and x86_64-musl. Works well on void.


      parent reply	other threads:[~2023-05-18  1:53 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-21 15:59 [PR PATCH] Subsurface adbrown101
2021-11-21 18:39 ` [PR REVIEW] Subsurface ericonr
2021-11-21 18:39 ` ericonr
2021-11-21 18:39 ` ericonr
2021-11-21 18:39 ` ericonr
2021-11-21 18:39 ` ericonr
2021-11-21 18:39 ` ericonr
2021-11-22 12:30 ` [PR PATCH] [Updated] Subsurface adbrown101
2021-11-22 13:45 ` adbrown101
2021-11-22 14:45 ` [PR REVIEW] Subsurface adbrown101
2021-11-22 14:45 ` adbrown101
2021-11-22 14:46 ` adbrown101
2021-11-22 14:46 ` adbrown101
2021-11-22 14:46 ` adbrown101
2021-11-22 14:46 ` adbrown101
2021-11-24  9:25 ` [PR PATCH] [Updated] Subsurface adbrown101
2021-11-24 12:08 ` [PR REVIEW] Subsurface adbrown101
2021-11-24 12:17 ` Subsurface adbrown101
2021-11-24 19:36 ` Subsurface Chocimier
2021-11-25 12:04 ` [PR PATCH] [Updated] Subsurface adbrown101
2021-11-25 12:52 ` adbrown101
2021-11-25 18:24 ` adbrown101
2021-11-25 18:27 ` Subsurface adbrown101
2021-11-25 19:31 ` Subsurface ericonr
2021-11-26  3:43 ` [PR REVIEW] Subsurface sgn
2021-11-26  3:52 ` Subsurface sgn
2021-11-26  4:24 ` Subsurface sgn
2021-11-26  4:28 ` [PR PATCH] [Updated] Subsurface sgn
2021-11-26 12:56 ` [PR REVIEW] Subsurface adbrown101
2021-11-26 13:08 ` [PR PATCH] [Updated] Subsurface adbrown101
2021-11-29 12:06 ` Subsurface adbrown101
2021-11-30 13:24 ` Subsurface adbrown101
2021-12-03 20:20 ` Subsurface adbrown101
2021-12-05 22:04 ` Subsurface adbrown101
2021-12-09 17:15 ` Subsurface adbrown101
2022-02-06 15:44 ` [PR PATCH] [Updated] Subsurface adbrown101
2022-02-06 15:47 ` Subsurface adbrown101
2022-02-08 12:15 ` [PR REVIEW] Subsurface adbrown101
2022-03-30 17:39 ` [PR PATCH] [Updated] Subsurface adbrown101
2022-04-24 13:18 ` adbrown101
2022-07-24  2:13 ` Subsurface github-actions
2022-07-26 18:39 ` [PR PATCH] [Updated] Subsurface adbrown101
2022-07-26 18:42 ` Subsurface adbrown101
2022-08-06 15:51 ` [PR PATCH] [Updated] Subsurface adbrown101
2022-08-07 15:51 ` adbrown101
2022-08-07 15:52 ` Subsurface adbrown101
2022-10-29 14:13 ` [PR PATCH] [Updated] Subsurface adbrown101
2022-10-29 16:06 ` adbrown101
2022-10-29 16:06 ` Subsurface adbrown101
2023-01-28  2:00 ` Subsurface github-actions
2023-02-01 12:26 ` [PR PATCH] [Updated] Subsurface adbrown101
2023-05-04  1:51 ` Subsurface github-actions
2023-05-18  1:52 ` 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=20230518015257.nZtz_VUbEK2u4B08-e6dKpyl-E_bUym4PF0UND54LBE@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).