On 01/02/2021 23:55, Simon Kelley wrote:
....>
I just committed another tweak, to get eg v2.65test1 and v2.65test11 in
the correct order.
Maybe the missing description of 2.84 could be added to CHANGELOG and
the resulting commit, exceptionally, re-tagged as 2.84?
Wouldn't this also avoid accidentally acquiring the rc2 tag, so making
tweaks to get-version moot (or postponing the need for a new tagging
scheme, according to taste) for now? Resulting binaries should be
functionally identical, except for pre-tweak builds where the output of
'dnsmasq --version', etc, would differ.
Eg:
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -1,3 +1,13 @@
+version 2.84
+ Fix a regression causing random log messages "failure to send
+ packet" and the loss of the associated DNS queries, after which a
+ retry would succeed, when dnsmasq was under fairly heavy load and
+ was configured for a mixture or IPv4 and IPv6 upstream DNS servers
+ or, possibly, was using --bind-interfaces.
+
+ Housekeeping (2021).
+
+
version 2.83
Use the values of --min-port and --max-port in outgoing
TCP connections to upstream DNS servers.
---
sort -k isn't a GNU extension: it's in POSIX.1.
/df
--
London SW6
UK
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
