From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Net-DNS 0.47 vs. 1.25
Date: Mon, 29 Jun 2020 10:57:05 +0100 [thread overview]
Message-ID: <BCE1240D-2548-43B2-85C3-B166CFB92A4D@ipfire.org> (raw)
In-Reply-To: <7f16c27e-3333-541f-9439-f199d127edbc@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
Hi,
> On 28 Jun 2020, at 19:54, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> is there a specific reason why we're still using 'Net-DNS 0.47', dated
> 01.04.2004?
No specific reason that I am aware of.
Please send patches :)
-Michael
> I built the current version (1.25, 26.06.2020) today, together with
> 'digest-hmac 1.03' and 'digest-sha1 2.13'. Especially the changelog for
> Net-DNS is really huge. After some rootfile adjustments all of them
> compiled without errors.
>
> But what made me wonder:
> Net-DNS didn't use the path .../xxxMACHINExxx-linux-thread-multi/...
> anymore, except for .../xxxMACHINExxx-linux-thread-multi/auto/...
>
> Could we use these updates? Or did I miss something?
>
> Opinions?
>
> Best,
> Matthias
prev parent reply other threads:[~2020-06-29 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 18:54 Matthias Fischer
2020-06-29 9:57 ` Michael Tremer [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=BCE1240D-2548-43B2-85C3-B166CFB92A4D@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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