Github messages for voidlinux
 help / color / mirror / Atom feed
From: jailbird777 <jailbird777@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: dnsdist-1.5.1
Date: Sat, 23 Jan 2021 04:44:32 +0100	[thread overview]
Message-ID: <20210123034432.QPj4H_gE0mUV2lfKf-ggdYaFdqOGenVAInesiy2lwds@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28109@inbox.vuxu.org>

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

New comment by jailbird777 on void-packages repository

https://github.com/void-linux/void-packages/pull/28109#issuecomment-765858633

Comment:
Good question! Other distros separate them out since postfix & powerDNS at least can both use tinycdb also, so that it's shared.  However, if there's no plans to add CDB support to postfix or to add pdns (I don't personally have use for pdns), I can drop tiyncdb completely and just use the built-in CDB code in dnsdist instead.  I'm fine with either one!

  parent reply	other threads:[~2021-01-23  3:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23  1:54 [PR PATCH] " jailbird777
2021-01-23  1:55 ` [PR PATCH] [Updated] " jailbird777
2021-01-23  1:59 ` jailbird777
2021-01-23  2:02 ` jailbird777
2021-01-23  2:04 ` jailbird777
2021-01-23  2:15 ` ericonr
2021-01-23  3:44 ` jailbird777 [this message]
2021-01-23 19:47 ` ericonr
2021-01-23 20:09 ` benalb
2021-03-11  1:08 ` [PR PATCH] [Updated] " jailbird777
2021-05-23  2:37 ` jailbird777
2021-05-23  3:04 ` [PR PATCH] [Updated] New package: dnsdist-1.6.0 ericonr
2021-07-01  7:15 ` jailbird777
2021-07-03  1:45 ` jailbird777
2021-07-09  5:18 ` jailbird777
2021-07-09 15:09 ` [PR REVIEW] " ericonr
2021-07-09 15:09 ` ericonr
2021-07-09 15:09 ` ericonr
2021-07-09 15:09 ` ericonr
2021-07-09 15:09 ` ericonr
2021-07-13  0:23 ` jailbird777
2021-07-13  0:23 ` [PR PATCH] [Closed]: " jailbird777

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=20210123034432.QPj4H_gE0mUV2lfKf-ggdYaFdqOGenVAInesiy2lwds@z \
    --to=jailbird777@users.noreply.github.com \
    --cc=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).