Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: selene-0.25.0
Date: Sat, 24 Jun 2023 14:44:42 +0200	[thread overview]
Message-ID: <20230624124442.5mEs63pPWwoozSE5QpYVvrxR7Ti1QUthWkl7w92l_Us@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39370@inbox.vuxu.org>

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

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

New package: selene-0.25.0
https://github.com/void-linux/void-packages/pull/39370

Description:
#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

#### Local build testing
- I built this PR locally for my native architecture, x86_64

We have a [Lua LSP](https://github.com/void-linux/void-packages/tree/master/srcpkgs/lua-language-server) and a [Lua formatter](https://github.com/void-linux/void-packages/tree/master/srcpkgs/StyLua) but no Lua linter afaics. I'm submitting this one since I use it personally.

      parent reply	other threads:[~2023-06-24 12:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 15:36 [PR PATCH] New package: selene-0.21.0 icp1994
2022-09-28  9:25 ` [PR PATCH] [Updated] " icp1994
2022-10-18 12:52 ` [PR PATCH] [Updated] New package: selene-0.21.1 icp1994
2022-12-08 10:02 ` [PR PATCH] [Updated] New package: selene-0.22.0 icp1994
2023-01-11  6:05 ` [PR PATCH] [Updated] New package: selene-0.23.1 icp1994
2023-01-11  6:28 ` icp1994
2023-04-12  1:52 ` New package: selene-0.24.0 github-actions
2023-04-12  6:11 ` [PR PATCH] [Updated] " icp1994
2023-06-24 12:44 ` Duncaen [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=20230624124442.5mEs63pPWwoozSE5QpYVvrxR7Ti1QUthWkl7w92l_Us@z \
    --to=duncaen@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).