Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnutls: update to 3.7.2
Date: Thu, 20 Jan 2022 01:44:46 +0100	[thread overview]
Message-ID: <20220120004446.fD554767O-nCyESh677FURqDLOlvKFNLUk3EBWJ8tFs@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: 669 bytes --]

New comment by paper42 on void-packages repository

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

Comment:
> @paper42 This PR is for a version of gnutls that is not from the stable branch ([3.6.16 release notes say "stable"](https://lists.gnupg.org/pipermail/gnutls-help/2021-May/004707.html), [3.7.3 release notes do not](https://lists.gnupg.org/pipermail/gnutls-help/2022-January/004736.html)). Is that alright?

Earlier today this was discussed on IRC in #xbps, most other distributions consider 3.7 to be stable enough including Debian and some applications now require this version, so I think we should just merge this update.

  parent reply	other threads:[~2022-01-20  0:44 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
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 [this message]
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=20220120004446.fD554767O-nCyESh677FURqDLOlvKFNLUk3EBWJ8tFs@z \
    --to=paper42@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).