Github messages for voidlinux
 help / color / mirror / Atom feed
From: carvalhudo <carvalhudo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] neovim-remote: update to 2.5.1
Date: Sun, 15 Jan 2023 03:11:10 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41659@inbox.vuxu.org> (raw)

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

There is a new pull request by carvalhudo against master on the void-packages repository

https://github.com/carvalhudo/void-packages update_neovim_remote
https://github.com/void-linux/void-packages/pull/41659

neovim-remote: update to 2.5.1
#### Testing the changes
- I tested the changes in this PR: **briefly**

A patch file from https://github.com/void-linux/void-packages/pull/41659.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update_neovim_remote-41659.patch --]
[-- Type: text/x-diff, Size: 1094 bytes --]

From 5c5c844711e9709eb8a8e71ed10b39d23a8ff2f0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20L=2E=20C=2E=20Moreira?= <alcm99@gmail.com>
Date: Sat, 14 Jan 2023 23:10:20 -0300
Subject: [PATCH] neovim-remote: update to 2.5.1

---
 srcpkgs/neovim-remote/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/neovim-remote/template b/srcpkgs/neovim-remote/template
index c510d263ec45..47f7eaa40d5f 100644
--- a/srcpkgs/neovim-remote/template
+++ b/srcpkgs/neovim-remote/template
@@ -1,6 +1,6 @@
 # Template file for 'neovim-remote'
 pkgname=neovim-remote
-version=2.4.0
+version=2.5.1
 revision=4
 build_style=python3-module
 hostmakedepends="python3-setuptools"
@@ -11,7 +11,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="https://github.com/mhinz/neovim-remote"
 distfiles="https://github.com/mhinz/neovim-remote/archive/v${version}.tar.gz"
-checksum=4213b6eaad638aa20d8687362764843beb626e6e1a03bc3c8b3399bbfc11fbf7
+checksum=cff04df8d82ea99168de441b23ee1ed21d64c6cb2196cb2e3d65a6778c14da01
 
 do_check() {
 	python3 -m pytest

             reply	other threads:[~2023-01-15  2:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15  2:11 carvalhudo [this message]
2023-01-15 20:40 ` [PR PATCH] [Updated] WIP: " carvalhudo
2023-01-21 19:24 ` carvalhudo
2023-01-21 19:28 ` carvalhudo
2023-01-21 19:29 ` carvalhudo
2023-01-21 19:39 ` carvalhudo
2023-01-21 19:57 ` carvalhudo
2023-01-21 19:57 ` carvalhudo
2023-01-21 20:31 ` carvalhudo
2023-04-22  1:53 ` github-actions
2023-05-07  1:57 ` [PR PATCH] [Closed]: " github-actions

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41659@inbox.vuxu.org \
    --to=carvalhudo@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).