Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cups: reverting to GnuTLS backend (fix broken new CUPS OpenSSL default IPPS issues)
Date: Tue, 18 Apr 2023 03:51:16 +0200	[thread overview]
Message-ID: <20230418015116.vBLjx76kKHm3itZKe-EkBpgDkiixh7ZhdgKirmxVJwE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41193@inbox.vuxu.org>

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

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/pull/41193#issuecomment-1512321671

Comment:
Pull Requests become stale 90 days after last activity and are closed 14 days after that.  If this pull request is still relevant bump it or assign it.

  parent reply	other threads:[~2023-04-18  1:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 21:03 [PR PATCH] re-enabled gnutls for cups since openssl IPPS printer server is faili… jpastuszek
2022-12-19 21:07 ` [PR PATCH] [Updated] Using GnuTLS for CUPS as TLS backend (fix broken new CUPS OpenSSL default) jpastuszek
2022-12-19 21:09 ` jpastuszek
2022-12-20 17:47 ` cups: reverting to GunTLS backend (fix broken new CUPS OpenSSL default IPPS issues) CameronNemo
2022-12-20 22:01 ` [PR PATCH] [Updated] " jpastuszek
2022-12-20 22:07 ` cups: reverting to GnuTLS " jpastuszek
2023-01-16 20:02 ` Vaelatern
2023-01-16 21:19 ` CameronNemo
2023-01-16 21:21 ` CameronNemo
2023-01-17  0:17 ` Piraty
2023-01-17  6:56 ` oynqr
2023-01-17  8:14 ` oynqr
2023-01-17 12:04 ` oynqr
2023-04-18  1:51 ` github-actions [this message]
2023-04-18 17:17 ` CameronNemo
2023-04-18 20:50 ` [PR PATCH] [Updated] " jpastuszek
2023-04-18 20:54 ` jpastuszek
2023-04-19 20:37 ` [PR PATCH] [Merged]: " Piraty

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=20230418015116.vBLjx76kKHm3itZKe-EkBpgDkiixh7ZhdgKirmxVJwE@z \
    --to=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).