Github messages for voidlinux
 help / color / mirror / Atom feed
From: bygoneNova <bygoneNova@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] neomutt: update to 20231221.
Date: Mon, 08 Jan 2024 17:14:18 +0100	[thread overview]
Message-ID: <20240108161418.a389-2qzDhAtFFddGqqS7-34Pel3I72gVrAlwWlVKTw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48124@inbox.vuxu.org>

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

There is an updated pull request by bygoneNova against master on the void-packages repository

https://github.com/bygoneNova/void-packages neomutt
https://github.com/void-linux/void-packages/pull/48124

neomutt: update to 20231221.
#### Testing the changes
- I tested the changes in this PR: **YES**

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

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

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

From 5feae3630e6d2f309f986a592c6cc78aa5bd447f Mon Sep 17 00:00:00 2001
From: bygoneNova <willow@bygonenova.dev>
Date: Mon, 8 Jan 2024 09:01:06 -0700
Subject: [PATCH] neomutt: update to 20231221.

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

diff --git a/srcpkgs/neomutt/template b/srcpkgs/neomutt/template
index bd26783394309..ed2f5967b6ed3 100644
--- a/srcpkgs/neomutt/template
+++ b/srcpkgs/neomutt/template
@@ -1,6 +1,6 @@
 # Template file for 'neomutt'
 pkgname=neomutt
-version=20231023
+version=20231221
 revision=2
 create_wrksrc=true
 build_wrksrc="${pkgname}-${version}"
@@ -22,7 +22,7 @@ homepage="https://neomutt.org/"
 _test_files_hash=00efc8388110208e77e6ed9d8294dfc333753d54
 distfiles="https://github.com/neomutt/neomutt/archive/${version}.tar.gz
  https://github.com/neomutt/neomutt-test-files/archive/${_test_files_hash}.tar.gz"
-checksum="2c3e9515d5810f9efd547d12b2301b9fa92d979aa8aa74a05780073f22c9bf0b
+checksum="b2add3823db78d8c0a86507ef3b244a3487d7e7a70c0d9e4e4b136acda9004d2
  2865e258034a72e498fdd1810071d9ab7559297a5f67203ea163cfdc4192dea4"
 python_version=3
 

  reply	other threads:[~2024-01-08 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 16:09 [PR PATCH] " bygoneNova
2024-01-08 16:14 ` bygoneNova [this message]
2024-01-08 16:19 ` [PR PATCH] [Updated] " bygoneNova
2024-01-31 15:49 ` [PR PATCH] [Merged]: " ahesford

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=20240108161418.a389-2qzDhAtFFddGqqS7-34Pel3I72gVrAlwWlVKTw@z \
    --to=bygonenova@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).