all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dale Mellor <guix-devel-0brg6a@rdmp.org>
To: 68621@debbugs.gnu.org
Subject: [bug#68621] [PATCH v2 0/4] Allow use of DNSSEC in knot-resolver service
Date: Tue, 23 Apr 2024 19:33:10 +0100	[thread overview]
Message-ID: <41e6590d7cd82331d8782e71782de90f049015ac.camel@rdmp.org> (raw)
In-Reply-To: <20240120212542.17473-1-hello@lnikki.la>

As per previous messages.




      parent reply	other threads:[~2024-04-23 18:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20 21:23 [bug#68621] [PATCH 0/2] Provide default DNSSEC trust anchors for knot-resolver Leo Nikkilä via Guix-patches via
2024-01-20 21:23 ` [bug#68620] [PATCH 1/2] gnu: knot-resolver: Re-enable default DNSSEC trust anchors Leo Nikkilä via Guix-patches via
2024-04-23 16:04   ` [bug#68620] Moved into 68621 Dale Mellor
2024-04-23 16:21   ` Dale Mellor
2024-01-20 21:23 ` [bug#68622] [PATCH 2/2] services: knot-resolver: Use default DNSSEC trust anchors Leo Nikkilä via Guix-patches via
2024-04-23 16:05   ` [bug#68622] Moved to 68621 Dale Mellor
2024-04-23 16:22   ` [bug#68622] Moved into 68621 Dale Mellor
2024-01-20 21:37 ` [bug#68621] [PATCH 0/2] Provide default DNSSEC trust anchors for knot-resolver Leo Nikkilä via Guix-patches via
2024-04-23 15:59 ` [bug#68621] Consolidating patches under this one issue number Dale Mellor
2024-04-23 16:12 ` [bug#68621] [PATCH v2 1/4] gnu: knot-resolver: Re-enable default DNSSEC trust anchors Dale Mellor
2024-04-23 16:12 ` [bug#68621] [PATCH v2 2/4] gnu: knot-resolver: Appease some guix lint complaints Dale Mellor
2024-04-23 16:12 ` [bug#68621] [PATCH v2 3/4] services: knot-resolver: Use default DNSSEC trust anchors Dale Mellor
2024-04-23 16:12 ` [bug#68621] [PATCH v2 4/4] gnu: knot-resolver: version to 5.7.2 Dale Mellor
2024-04-23 18:33 ` Dale Mellor [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

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

  git send-email \
    --in-reply-to=41e6590d7cd82331d8782e71782de90f049015ac.camel@rdmp.org \
    --to=guix-devel-0brg6a@rdmp.org \
    --cc=68621@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.