<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="monospace">agreed (2)</font><br>
</p>
<div class="moz-cite-prefix">On 15.06.21 17:12, David Patte via tz
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3879dcbf-c604-7f28-84b8-5fa3c2837936@relativedata.com">agreed
<br>
<br>
On 2021-06-15 10:56, Stephen Colebourne via tz wrote:
<br>
<blockquote type="cite">On Mon, 14 Jun 2021 at 08:18, Paul Eggert
<a class="moz-txt-link-rfc2396E" href="mailto:eggert@cs.ucla.edu"><eggert@cs.ucla.edu></a> wrote:
<br>
<blockquote type="cite">On 6/10/21 4:28 PM, Stephen Colebourne
via tz wrote:
<br>
<br>
<blockquote type="cite">If a statement is to be made it should
be in both news and theory.
<br>
</blockquote>
Sure, that could be done. Proposed draft attached. I have not
installed
<br>
this in the development sources.
<br>
</blockquote>
The patch is fine so far as it goes. But it makes a mockery of
not
<br>
reverting the merging patch under discussion.
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">- revert the patch and any previous
patches that merged zones across
<br>
country borders
<br>
</blockquote>
This alternative is less appealing, for reasons already
discussed. I
<br>
think we're better off with a technical compromise, such as
'make'
<br>
one-liner mentioned above, or something like the compromise I
suggested
<br>
at the start of this thread
<br>
<a class="moz-txt-link-rfc2396E" href="https://mm.icann.org/pipermail/tz/2021-June/030220.html"><https://mm.icann.org/pipermail/tz/2021-June/030220.html></a>.
<br>
</blockquote>
We seem to be at an impasse.
<br>
<br>
I don't think there is any support from the mailing list for the
<br>
merging patch to remain in the repo. You've had many requests to
<br>
revert it, and no requests to retain it.
<br>
<br>
There are technical solutions available to reduce the amount of
data
<br>
published to downstream users, but the starting point must be a
fully
<br>
populated database, not one that is logically broken. The next
action
<br>
must be to revert. Then we can agree on any technical measures
<br>
necessary.
<br>
<br>
Stephen
<br>
</blockquote>
</blockquote>
</body>
</html>