From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: [Dnsmasq-discuss] Announce: dnsmasq-2.73rc1
Date: Mon, 23 Mar 2015 15:13:46 +0000 [thread overview]
Message-ID: <55102DAA.7010501@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw5ZfDAgmts6gcv+1Py5BRxyeNFVE-PX_SkmCF+3KN6kqA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 324 bytes --]
On 20/03/2015 02:33, Dave Taht wrote:
> dang it, now I guess I have yet another reason to do a new release of
> cero. Nicely elegant dnssec timestamp fix, in particular.
Have to agree, Simon did a superb implementation! Solved a major
stumbling block with enabling dnssec on Asuswrt.
Hoping openwrt updates soon.
[-- Attachment #1.2: Type: text/html, Size: 604 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]
prev parent reply other threads:[~2015-03-23 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <550B5ED4.7000003@thekelleys.org.uk>
2015-03-20 2:33 ` Dave Taht
2015-03-23 15:13 ` Kevin Darbyshire-Bryant [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://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55102DAA.7010501@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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