From: brihadeesh <brihadeesh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: sov-0.72
Date: Thu, 24 Nov 2022 10:08:00 +0100 [thread overview]
Message-ID: <20221124090800.IGt1n16jDoiMhWOY1gsu2rkTxBhkqsw5g_aNExncw5M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36970@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
New comment by brihadeesh on void-packages repository
https://github.com/void-linux/void-packages/pull/36970#issuecomment-1326153140
Comment:
Hi, @abenson I've updated the template to reflect the 0.73 which is one version number behind the current release. The latest release i.e. 0.74 doesn't appear to build and I think I might have to get that fixed upstream.
next prev parent reply other threads:[~2022-11-24 9:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 9:31 [PR PATCH] New package: sov-0.63 brihadeesh
2022-05-04 20:43 ` [PR REVIEW] " abenson
2022-05-05 4:57 ` brihadeesh
2022-05-05 5:01 ` [PR PATCH] [Updated] " brihadeesh
2022-05-05 5:04 ` [PR REVIEW] " brihadeesh
2022-08-07 2:14 ` github-actions
2022-08-07 9:58 ` brihadeesh
2022-08-07 10:02 ` [PR REVIEW] " paper42
2022-08-07 10:02 ` paper42
2022-08-07 10:10 ` brihadeesh
2022-08-07 10:17 ` paper42
2022-08-07 10:47 ` [PR PATCH] [Updated] " brihadeesh
2022-08-07 10:52 ` brihadeesh
2022-08-07 10:59 ` [PR PATCH] [Updated] " brihadeesh
2022-08-07 11:02 ` brihadeesh
2022-08-07 11:03 ` brihadeesh
2022-08-24 10:16 ` brihadeesh
2022-08-24 11:21 ` abenson
2022-08-24 11:22 ` abenson
2022-08-24 11:30 ` [PR PATCH] [Updated] " brihadeesh
2022-08-24 11:50 ` brihadeesh
2022-08-24 11:53 ` brihadeesh
2022-11-23 2:06 ` github-actions
2022-11-24 8:59 ` [PR PATCH] [Updated] " brihadeesh
2022-11-24 9:04 ` [PR PATCH] [Updated] New package: sov-0.72 brihadeesh
2022-11-24 9:08 ` brihadeesh [this message]
2023-02-24 2:00 ` New package: sov-0.73 github-actions
2023-03-10 2:05 ` [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=20221124090800.IGt1n16jDoiMhWOY1gsu2rkTxBhkqsw5g_aNExncw5M@z \
--to=brihadeesh@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).