unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: zimoun <zimon.toutoune@gmail.com>, control@debbugs.gnu.org
Cc: Mathieu Othacehe <othacehe@gnu.org>,
	Andreas Enge <andreas@enge.fr>,
	30619-done@debbugs.gnu.org
Subject: bug#30619: Cuirass requires TLS certificates
Date: Fri, 21 Jan 2022 11:44:10 +0100	[thread overview]
Message-ID: <0f5d7f7984633b3fca6a732ec608f9a964d9fe1e.camel@telenet.be> (raw)
In-Reply-To: <61df0fdc1a0db3ec42f2a03500333b0a1bbaa2eb.camel@telenet.be>

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

bugs 30619 + donewontfix
thanks

> [various discussion]

While I believe a 'certificates' field or the like would be nice,
there does not appear to be a need or interest, hence closing.

If someone would like to implement some solution or has a need,
they can reopen the bug (see
<https://debbugs.gnu.org/server-control.html>).

Greetings,
Maxime.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2022-01-21 11:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 20:51 bug#30619: Cuirass requires TLS certificates Andreas Enge
2018-02-27 16:00 ` Ludovic Courtès
2021-09-16  7:33   ` zimoun
2021-10-12 21:57     ` zimoun
2021-10-15 15:20       ` Ludovic Courtès
2021-11-26  1:38         ` zimoun
2021-11-26  6:28           ` Maxime Devos
2021-11-26  6:31             ` Maxime Devos
2021-11-26  6:32             ` Maxime Devos
2022-01-04 23:09             ` zimoun
2022-01-05  9:53               ` Maxime Devos
2022-01-21 10:44                 ` Maxime Devos [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f5d7f7984633b3fca6a732ec608f9a964d9fe1e.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=30619-done@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=control@debbugs.gnu.org \
    --cc=othacehe@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).