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]: [WIP] New package: etlegacy-2.81.1
Date: Sat, 08 Jul 2023 04:05:44 +0200	[thread overview]
Message-ID: <20230708020544.x0NBPtDlOoLsGDSIKoFX7T1IpP4AfQ1XfJsiSAIP7Dw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32824@inbox.vuxu.org>

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

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

[WIP] New package: etlegacy-2.81.1
https://github.com/void-linux/void-packages/pull/32824

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?
- [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-glib)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->
[closes https://github.com/void-linux/void-packages/issues/32406]

      parent reply	other threads:[~2023-07-08  2:05 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 19:07 [PR PATCH] New package: etlegacy-2.77.1 biopsin
2021-09-03 19:34 ` [PR PATCH] [Updated] " biopsin
2021-09-03 20:05 ` [PR REVIEW] " Chocimier
2021-09-03 20:05 ` Chocimier
2021-09-03 20:05 ` Chocimier
2021-09-03 20:11 ` biopsin
2021-09-04 18:17 ` biopsin
2021-09-04 18:24 ` Chocimier
2021-09-04 18:27 ` [PR REVIEW] " q66
2021-09-04 18:38 ` biopsin
2021-09-04 20:16 ` ericonr
2021-09-04 20:47 ` biopsin
2021-09-04 20:50 ` biopsin
2021-09-07 13:54 ` [PR REVIEW] " biopsin
2021-09-11 15:09 ` [PR PATCH] [Updated] " biopsin
2021-09-11 15:20 ` [PR PATCH] [Updated] [WIP] " biopsin
2021-09-11 15:28 ` biopsin
2021-09-12  9:02 ` biopsin
2021-09-12  9:03 ` biopsin
2021-09-12 16:31 ` [PR REVIEW] " q66
2021-09-12 16:31 ` q66
2021-09-12 18:21 ` [PR PATCH] [Updated] " biopsin
2021-09-12 18:23 ` [PR REVIEW] " biopsin
2021-09-12 18:26 ` biopsin
2021-09-12 21:26 ` q66
2021-09-12 21:26 ` q66
2021-09-13  5:45 ` [PR PATCH] [Updated] " biopsin
2021-09-13  6:16 ` biopsin
2021-09-13 12:39 ` q66
2021-09-13 12:42 ` q66
2021-09-13 12:44 ` q66
2021-09-13 12:46 ` q66
2021-09-13 16:15 ` biopsin
2021-09-13 17:16 ` [PR REVIEW] " Chocimier
2021-09-13 17:16 ` Chocimier
2021-09-13 17:16 ` Chocimier
2021-09-13 17:16 ` Chocimier
2021-09-13 17:16 ` Chocimier
2021-09-13 17:16 ` Chocimier
2021-09-14  6:57 ` [PR PATCH] [Updated] " biopsin
2021-10-01 17:40 ` [PR PATCH] [Updated] " biopsin
2021-10-01 17:41 ` biopsin
2021-10-01 18:19 ` biopsin
2021-10-01 19:48 ` [PR PATCH] [Updated] " biopsin
2021-10-04  7:01 ` biopsin
2021-10-04 16:20 ` [PR REVIEW] New package: etlegacy-2.78.0 Chocimier
2021-10-04 18:25 ` [PR PATCH] [Updated] " biopsin
2021-10-04 18:26 ` [PR REVIEW] " biopsin
2021-11-03 11:49 ` [PR PATCH] [Updated] " biopsin
2021-12-26  9:22 ` [PR PATCH] [Updated] New package: etlegacy-2.78.1 biopsin
2022-04-13  6:03 ` [PR PATCH] [Updated] New package: etlegacy-2.79.0 biopsin
2022-07-13  2:15 ` github-actions
2022-07-13  7:07 ` [PR PATCH] [Updated] " biopsin
2022-07-13  7:11 ` [WIP] New package: etlegacy-2.80.2 biopsin
2022-07-13  7:11 ` [PR PATCH] [Updated] " biopsin
2022-07-13  7:15 ` biopsin
2022-07-13  7:17 ` biopsin
2022-09-18 13:29 ` biopsin
2022-09-20  9:12 ` atk
2022-09-20 11:22 ` biopsin
2022-09-21 19:24 ` rafal1137
2022-11-29 12:43 ` atk
2023-02-28  2:01 ` github-actions
2023-02-28 12:29 ` rafal1137
2023-03-25 10:09 ` [PR PATCH] [Updated] " biopsin
2023-03-25 10:30 ` [WIP] New package: etlegacy-2.81.1 biopsin
2023-06-24  2:05 ` github-actions
2023-07-08  2:05 ` 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=20230708020544.x0NBPtDlOoLsGDSIKoFX7T1IpP4AfQ1XfJsiSAIP7Dw@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).