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: splatmoji-1.2.0
Date: Wed, 01 Jun 2022 04:14:15 +0200	[thread overview]
Message-ID: <20220601021415.g8hSVBEKt1n9P4Tp9hS9Q-TZFhdDORajbH6SXbLK8F4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30025@inbox.vuxu.org>

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

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

New package: splatmoji-1.2.0
https://github.com/void-linux/void-packages/pull/30025

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? 
Yes, and should work for all architectures since it's actually a shell script

      parent reply	other threads:[~2022-06-01  2:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 22:21 [PR PATCH] " chilledfrogs
2021-04-05 22:28 ` [PR REVIEW] " abenson
2021-04-05 22:28 ` abenson
2021-04-05 22:30 ` abenson
2021-04-05 22:32 ` abenson
2021-04-05 22:41 ` abenson
2021-04-05 22:44 ` chilledfrogs
2021-04-05 22:45 ` chilledfrogs
2021-04-05 22:45 ` chilledfrogs
2021-04-05 22:45 ` chilledfrogs
2021-04-05 22:45 ` chilledfrogs
2021-04-05 22:46 ` chilledfrogs
2021-04-05 22:49 ` [PR PATCH] [Updated] " chilledfrogs
2021-04-05 22:51 ` [PR REVIEW] " chilledfrogs
2021-04-05 22:54 ` [PR PATCH] [Updated] " chilledfrogs
2021-04-05 22:54 ` [PR REVIEW] " abenson
2021-04-05 23:17 ` chilledfrogs
2021-04-05 23:17 ` chilledfrogs
2021-04-30 21:27 ` chilledfrogs
2021-04-30 21:33 ` [PR PATCH] [Updated] " chilledfrogs
2021-04-30 21:41 ` [PR REVIEW] " abenson
2021-05-01  1:43 ` chilledfrogs
2021-05-01 15:15 ` Piraty
2021-05-01 21:37 ` chilledfrogs
2021-05-02 21:58 ` [PR PATCH] [Updated] " chilledfrogs
2021-05-02 22:00 ` chilledfrogs
2021-05-02 22:00 ` [PR REVIEW] " chilledfrogs
2022-05-17  2:14 ` github-actions
2022-06-01  2:14 ` 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=20220601021415.g8hSVBEKt1n9P4Tp9hS9Q-TZFhdDORajbH6SXbLK8F4@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).