Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnutls: update to 3.7.2
Date: Wed, 12 Jan 2022 01:33:06 +0100	[thread overview]
Message-ID: <20220112003306.sFKZOyluv4sfYq2Ge8yseY2xHpmUKPg5lrS9Txd1jRU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34742@inbox.vuxu.org>

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

New comment by cinerea0 on void-packages repository

https://github.com/void-linux/void-packages/pull/34742#issuecomment-1010508042

Comment:
I didn't realize that gnutls followed the same versioning conventions as GNOME projects where odd minor versions aren't considered stable releases, but looking at the release notes for 3.6.16 vs 3.7.2 it definitely does. I created this PR after the old one was closed because the new version is required to update filezilla. Since that isn't a package that needs to be kept perfectly up to date I understand if that's not a good reason to ignore policy.

  parent reply	other threads:[~2022-01-12  0:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28 19:45 [PR PATCH] " cinerea0
2021-12-28 19:47 ` cinerea0
2022-01-11 19:48 ` ericonr
2022-01-12  0:33 ` cinerea0 [this message]
2022-01-20  0:30 ` [PR REVIEW] " paper42
2022-01-20  0:33 ` paper42
2022-01-20  0:39 ` cinerea0
2022-01-20  0:44 ` paper42
2022-01-20  2:00 ` [PR PATCH] [Updated] " cinerea0
2022-01-20  5:35 ` gnutls: update to 3.7.3 ericonr
2022-01-20  5:37 ` [PR PATCH] [Closed]: " ericonr
2022-01-20  5:38 ` ericonr
  -- strict thread matches above, loose matches on Subject: below --
2021-11-27 11:25 [PR PATCH] gnutls: update to 3.7.2 dotnetfox
2021-12-18  1:47 ` cinerea0
2021-12-28 16:34 ` dotnetfox

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=20220112003306.sFKZOyluv4sfYq2Ge8yseY2xHpmUKPg5lrS9Txd1jRU@z \
    --to=cinerea0@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    --subject='Re: gnutls: update to 3.7.2' \
    /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

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).