<html lang='en'>
<head>
<meta content='text/html; charset=utf-8' http-equiv='Content-Type'>
<title>
GitLab
</title>
</meta>
</head>
<style>
img {
max-width: 100%;
height: auto;
}
p.details {
font-style:italic;
color:#777
}
.footer p {
font-size:small;
color:#777
}
pre.commit-message {
white-space: pre-wrap;
}
.file-stats a {
text-decoration: none;
}
.file-stats .new-file {
color: #090;
}
.file-stats .deleted-file {
color: #B00;
}
</style>
<body>
<div class='content'>
<h3>Hal Murray pushed to branch master at <a href="https://gitlab.com/NTPsec/ntpsec">NTPsec / ntpsec</a></h3>
<h4>
Commits:
</h4>
<ul>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/94dc3a1c997b3d6b98d2f72856416df5cadd4f60">94dc3a1c</a></strong>
<div>
<span>by Hal Murray</span>
<i>at 2015-12-06T22:02:00Z</i>
</div>
<pre class='commit-message'>Fix "the the" typos
Including in comments in code.</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/f723fcb4922d88591676743a0742bf16652a6cec">f723fcb4</a></strong>
<div>
<span>by Hal Murray</span>
<i>at 2015-12-06T22:09:50Z</i>
</div>
<pre class='commit-message'>Merge branch 'master' of gitlab.com:NTPsec/ntpsec</pre>
</li>
</ul>
<h4>22 changed files:</h4>
<ul>
<li class='file-stats'>
<a href='#diff-0'>
docs/autokey.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-1'>
docs/clock.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-2'>
docs/cluster.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-3'>
docs/confopt.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-4'>
docs/decode.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-5'>
docs/driver28.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-6'>
docs/miscopt.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-7'>
docs/oncore-shmem.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-8'>
docs/parsenew.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-9'>
docs/poll.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-10'>
docs/prefer.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-11'>
docs/stats.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-12'>
docs/xleave.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-13'>
include/ntp_net.h
</a>
</li>
<li class='file-stats'>
<a href='#diff-14'>
libisc/win32/interfaceiter.c
</a>
</li>
<li class='file-stats'>
<a href='#diff-15'>
ntpd/ntp_leapsec.c
</a>
</li>
<li class='file-stats'>
<a href='#diff-16'>
ntpd/ntp_leapsec.h
</a>
</li>
<li class='file-stats'>
<a href='#diff-17'>
ntpd/ntp_proto.c
</a>
</li>
<li class='file-stats'>
<a href='#diff-18'>
ntpd/refclock_arc.c
</a>
</li>
<li class='file-stats'>
<a href='#diff-19'>
ntpd/refclock_mx4200.c
</a>
</li>
<li class='file-stats'>
<a href='#diff-20'>
ntpd/refclock_oncore.c
</a>
</li>
<li class='file-stats'>
<a href='#diff-21'>
util/calc_tickadj/calc_tickadj.txt
</a>
</li>
</ul>
<h4>Changes:</h4>
<li id='diff-0'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-0'>
<strong>
docs/autokey.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/autokey.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/autokey.txt
</span><span style="color: #aaaaaa">@@ -91,7 +91,7 @@ produced by commercial services, utility programs in the OpenSSL
</span> software library, and the link:keygen.html[{ntpkeygen}] utility program
in the NTP software distribution. A certificate includes the subject
name of the client, the issuer name of the server, the public key of the
<span style="color: #000000;background-color: #ffdddd">-client and the time period over which the the public and private keys
</span><span style="color: #000000;background-color: #ddffdd">+client and the time period over which the public and private keys
</span> are valid. All Autokey hosts have a self-signed certificate with the
Autokey name as both the subject and issuer. During the protocol,
additional certificates are produced with the Autokey host name as
<span style="color: #aaaaaa">@@ -384,7 +384,7 @@ the filestamp suppressed. Thus, the nonencryted parameters file from
</span> each TA is copied to X with this name.
To complete the configuration, the TH includes the client parameters
<span style="color: #000000;background-color: #ffdddd">-file name in the +ident+ option of the the +server+ command for the TA
</span><span style="color: #000000;background-color: #ddffdd">+file name in the +ident+ option of the +server+ command for the TA
</span> association
+server 1.2.3.4 ident group,+
<span style="color: #aaaaaa">@@ -400,7 +400,7 @@ can be configured using more than one cryptotype combination, although
</span> not all combinations are interoperable. Note however that some
cryptotype combinations may successfully intemperate with each other,
but may not represent good security practice. The server and client
<span style="color: #000000;background-color: #ffdddd">-cryptotypes are defined by the the following codes.
</span><span style="color: #000000;background-color: #ddffdd">+cryptotypes are defined by the following codes.
</span>
NONE::
A client or server is type NONE if authentication is not available or
</code></pre>
<br>
</li>
<li id='diff-1'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-1'>
<strong>
docs/clock.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/clock.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/clock.txt
</span><span style="color: #aaaaaa">@@ -88,7 +88,7 @@ the TOY chip clock has drifted significantly from NTP time. This can
</span> cause a transient at system startup. In the past, this has produced a
phase transient and resulted in a frequency surge that could take some
time, even hours, to subside. When the highest accuracy is required,
<span style="color: #000000;background-color: #ffdddd">-some means is necessary to manage the startup process so that the the
</span><span style="color: #000000;background-color: #ddffdd">+some means is necessary to manage the startup process so that the
</span> clock is quickly set correctly and the frequency is undisturbed. The
hold timer is used to suppress frequency adjustments during the training
and startup intervals described below. At the beginning of the interval
<span style="color: #aaaaaa">@@ -141,7 +141,7 @@ Sync Interval::
</span>
The state machine consists of five states. An event is created when an
update is received by the discipline algorithm. Depending on the state
<span style="color: #000000;background-color: #ffdddd">-and the the offset magnitude, the machine performs some actions and
</span><span style="color: #000000;background-color: #ddffdd">+and the offset magnitude, the machine performs some actions and
</span> transitions to the same or another state. Following is a short
description of the states.
</code></pre>
<br>
</li>
<li id='diff-2'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-2'>
<strong>
docs/cluster.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/cluster.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/cluster.txt
</span><span style="color: #aaaaaa">@@ -61,7 +61,7 @@ jitter dominates peer jitter,the algorithm prunes candidate 1. In (b),
</span> pruning additional candidates does not reduce select jitter, the
algorithm terminates with candidates 2, 3 and 4 as survivors.
<span style="color: #000000;background-color: #ffdddd">-The survivor list is passed on to the the mitigation algorithms, which
</span><span style="color: #000000;background-color: #ddffdd">+The survivor list is passed on to the mitigation algorithms, which
</span> combine the survivors, select a system peer, and compute the system
statistics passed on to dependent clients. Note the use of root distance
λ as a weight factor at each round in the clock cluster algorithm. This
</code></pre>
<br>
</li>
<li id='diff-3'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-3'>
<strong>
docs/confopt.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/confopt.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/confopt.txt
</span><span style="color: #aaaaaa">@@ -72,7 +72,7 @@ include::includes/assoc-options.txt[]
</span> == Auxiliary Commands ==
Information on authentication for broadcast, manycast, and
<span style="color: #000000;background-color: #ffdddd">-manycat options can be found at link:authopt.html[Authentication Options].
</span><span style="color: #000000;background-color: #ddffdd">+manycast options can be found at link:authopt.html[Authentication Options].
</span>
include::includes/assoc-auxcommands.txt[]
</code></pre>
<br>
</li>
<li id='diff-4'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-4'>
<strong>
docs/decode.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/decode.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/decode.txt
</span><span style="color: #aaaaaa">@@ -139,7 +139,7 @@ of the +rv associd+ display produced by the +{ntpq}+ program.
</span>
The Status Field displays the peer status code bits in hexadecimal; each
bit is an independent flag. (Note this field is 5 bits wide, and
<span style="color: #000000;background-color: #ffdddd">-combines with the the 3-bit-wide Select Field to create the first full
</span><span style="color: #000000;background-color: #ddffdd">+combines with the 3-bit-wide Select Field to create the first full
</span> byte of the peer status word.) The meaning of each bit in the Status
Field is listed in the following table:
</code></pre>
<br>
</li>
<li id='diff-5'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-5'>
<strong>
docs/driver28.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/driver28.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/driver28.txt
</span><span style="color: #aaaaaa">@@ -109,7 +109,7 @@ The 4th field is the number of second ticks since the last poll. The 5th
</span> field is the number of good data samples found. The last 64 will be used
by _{ntpd}_. The 6th field is the number of sample that didn't have valid
data ready. The 7th field is the number of bad samples. The 8th field is
<span style="color: #000000;background-color: #ffdddd">-the number of times the the mode 1 info was update while _{ntpd}_ was
</span><span style="color: #000000;background-color: #ddffdd">+the number of times the mode 1 info was update while _{ntpd}_ was
</span> trying to grab a sample.
Here is a sample showing the GPS reception fading out:
</code></pre>
<br>
</li>
<li id='diff-6'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-6'>
<strong>
docs/miscopt.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/miscopt.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/miscopt.txt
</span><span style="color: #aaaaaa">@@ -23,7 +23,7 @@ include::includes/misc-options.txt[]
</span> // If you change this, be very sure to keep that synchronized.
+tos+ [+beacon+ 'beacon' | +ceiling+ 'ceiling' | +cohort+ {+0+ | +1+} | +floor+ 'floor' | +maxclock+ 'maxclock' | +maxdist+ 'maxdist' | +minclock+ 'minclock' | +mindist+ 'mindist' | +minsane+ 'minsane' | +orphan+ 'stratum' | +orphanwait+ 'delay']::
<span style="color: #000000;background-color: #ffdddd">- This command alters certain system variables used by the the clock
</span><span style="color: #000000;background-color: #ddffdd">+ This command alters certain system variables used by the clock
</span> selection and clustering algorithms. The default values of these
variables have been carefully optimized for a wide range of network
speeds and reliability expectations. Very rarely is it necessary to
</code></pre>
<br>
</li>
<li id='diff-7'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-7'>
<strong>
docs/oncore-shmem.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/oncore-shmem.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/oncore-shmem.txt
</span><span style="color: #aaaaaa">@@ -126,7 +126,7 @@ better accuracy. In 0D mode no position is calculated.
</span>
When the SHMEM option is active, and if one of *Posn2D* or *Posn3D* is
specified, one @@Ea record is hijacked each 15s, and the receiver is put
<span style="color: #000000;background-color: #ffdddd">-back in 2D/3D mode so the the current location can be determined (for
</span><span style="color: #000000;background-color: #ddffdd">+back in 2D/3D mode so the current location can be determined (for
</span> position determination, or for tracking SA). The timekeeping code is
careful NOT to use the time associated with this (less accurate) 2D/3D
tick in its timekeeping functions.
</code></pre>
<br>
</li>
<li id='diff-8'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-8'>
<strong>
docs/parsenew.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/parsenew.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/parsenew.txt
</span><span style="color: #aaaaaa">@@ -44,7 +44,7 @@ following values can be OR'ed together:
</span> PARSEB_POWERUP no synchronisation - clock confused (must set then)
PARSEB_NOSYNC timecode currently not confirmed (must set then)
usually on reception error when there is still a
<span style="color: #000000;background-color: #ffdddd">- chance the the generated time is still ok.
</span><span style="color: #000000;background-color: #ddffdd">+ chance the generated time is still ok.
</span>
PARSEB_DST DST in effect (informational only)
PARSEB_UTC timecode contains UTC time (informational only)
</code></pre>
<br>
</li>
<li id='diff-9'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-9'>
<strong>
docs/poll.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/poll.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/poll.txt
</span><span style="color: #aaaaaa">@@ -16,7 +16,7 @@ a jiggle counter, which is initially set to zero. When a clock update is
</span> received and the offset exceeds the clock jitter by a factor of 4, the
jiggle counter is increased by the poll exponent; otherwise, it is
decreased by twice the poll exponent. If the jiggle counter is greater
<span style="color: #000000;background-color: #ffdddd">-than an arbitrary threshold of 30, it is reset to 0 and the the poll
</span><span style="color: #000000;background-color: #ddffdd">+than an arbitrary threshold of 30, it is reset to 0 and the poll
</span> exponent is increased by 1. If the jiggle counter is less than -30, it
is set to 0 and the poll exponent decreased by 1. In effect, the
algorithm has a relatively slow reaction to good news, but a relatively
</code></pre>
<br>
</li>
<li id='diff-10'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-10'>
<strong>
docs/prefer.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/prefer.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/prefer.txt
</span><span style="color: #aaaaaa">@@ -183,7 +183,7 @@ prefer peer is among the survivors, the combine algorithm is not used.
</span> Instead, the offset and jitter of the prefer peer are used exclusively
as the final values. In the common case involving a radio clock and a
flock of remote backup servers, and with the radio clock designated a
<span style="color: #000000;background-color: #ffdddd">-prefer peer, the the radio clock disciplines the system clock as long as
</span><span style="color: #000000;background-color: #ddffdd">+prefer peer, the radio clock disciplines the system clock as long as
</span> the radio itself remains operational. However, if the radio fails or
becomes a falseticker, the combined backup sources continue to
discipline the system clock.
</code></pre>
<br>
</li>
<li id='diff-11'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-11'>
<strong>
docs/stats.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/stats.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/stats.txt
</span><span style="color: #aaaaaa">@@ -61,7 +61,7 @@ offset, delay and dispersion are called the sample statistics.
</span>
[NOTE]
In very fast networks where the client clock frequency is not
<span style="color: #000000;background-color: #ffdddd">-within 1 PPM or so of the the server clock frequency, the roundtrip
</span><span style="color: #000000;background-color: #ddffdd">+within 1 PPM or so of the server clock frequency, the roundtrip
</span> delay may have small negative values. This is usually a temporary
condition when the client is first started. When using the roundtrip
delay in calculations, negative values are assumed zero.
</code></pre>
<br>
</li>
<li id='diff-12'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-12'>
<strong>
docs/xleave.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/xleave.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/xleave.txt
</span><span style="color: #aaaaaa">@@ -25,7 +25,7 @@ In other words, we would like to replace the transmit softstamp with a
</span> drivestamp, but the problem is the transmit drivestamp is available only
after the packet has been sent. A solution for this problem is the
two-step or interleaved protocol described on this page and included in
<span style="color: #000000;background-color: #ffdddd">-the the current reference implementation. In interleaved modes the
</span><span style="color: #000000;background-color: #ddffdd">+the current reference implementation. In interleaved modes the
</span> transmit drivestamp for one packet is actually carried in the
immediately following packet. The trick, however, is to implement the
interleaved protocol without changing the NTP packet header format,
</code></pre>
<br>
</li>
<li id='diff-13'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-13'>
<strong>
include/ntp_net.h
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/include/ntp_net.h
</span><span style="color: #000000;background-color: #ddffdd">+++ b/include/ntp_net.h
</span><span style="color: #aaaaaa">@@ -211,7 +211,7 @@ typedef union {
</span> /*
* Macro for checking for invalid addresses. This is really, really
* gross, but is needed so no one configures a host on net 127 now that
<span style="color: #000000;background-color: #ffdddd">- * we're encouraging it the the configuration file.
</span><span style="color: #000000;background-color: #ddffdd">+ * we're encouraging it the configuration file.
</span> */
#define LOOPBACKADR 0x7f000001
#define LOOPNETMASK 0xff000000
</code></pre>
<br>
</li>
<li id='diff-14'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-14'>
<strong>
libisc/win32/interfaceiter.c
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/libisc/win32/interfaceiter.c
</span><span style="color: #000000;background-color: #ddffdd">+++ b/libisc/win32/interfaceiter.c
</span><span style="color: #aaaaaa">@@ -81,7 +81,7 @@ static PGETADAPTERSADDRESSES pGAA;
</span> /* Common utility functions */
/*
<span style="color: #000000;background-color: #ffdddd">- * Windows always provides 255.255.255.255 as the the broadcast
</span><span style="color: #000000;background-color: #ddffdd">+ * Windows always provides 255.255.255.255 as the broadcast
</span> * address. ntpd needs to know the broadcast address which will target
* only that network interface, not all. Reconstruct it from the
* address and mask.
</code></pre>
<br>
</li>
<li id='diff-15'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-15'>
<strong>
ntpd/ntp_leapsec.c
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/ntpd/ntp_leapsec.c
</span><span style="color: #000000;background-color: #ddffdd">+++ b/ntpd/ntp_leapsec.c
</span><span style="color: #aaaaaa">@@ -964,7 +964,7 @@ do_hash_data(
</span> isc_sha1_update(mdctx, text, tlen);
}
<span style="color: #000000;background-color: #ffdddd">-/* given a reader and a reader arg, calculate and validate the the hash
</span><span style="color: #000000;background-color: #ddffdd">+/* given a reader and a reader arg, calculate and validate the hash
</span> * signature of a NIST leap second file.
*/
int
</code></pre>
<br>
</li>
<li id='diff-16'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-16'>
<strong>
ntpd/ntp_leapsec.h
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/ntpd/ntp_leapsec.h
</span><span style="color: #000000;background-color: #ddffdd">+++ b/ntpd/ntp_leapsec.h
</span><span style="color: #aaaaaa">@@ -77,7 +77,7 @@ extern bool leapsec_electric(electric_mode el);
</span> * 'tai_offs' is the CURRENT distance from clock (UTC) to TAI. Always valid.
* 'tai_diff' is the change in TAI offset after the next leap
* transition. Zero if nothing is pending or too far ahead.
<span style="color: #000000;background-color: #ffdddd">- * 'warped' is set only once, when the the leap second occurred between
</span><span style="color: #000000;background-color: #ddffdd">+ * 'warped' is set only once, when the leap second occurred between
</span> * two queries. Always zero in electric mode. If non-zero,
* immediately step the clock.
* 'proximity' is a proximity warning. See definitions below. This is
</code></pre>
<br>
</li>
<li id='diff-17'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-17'>
<strong>
ntpd/ntp_proto.c
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/ntpd/ntp_proto.c
</span><span style="color: #000000;background-color: #ddffdd">+++ b/ntpd/ntp_proto.c
</span><span style="color: #aaaaaa">@@ -2391,7 +2391,7 @@ clock_filter(
</span> peer->jitter = max(SQRT(peer->jitter), LOGTOD(sys_precision));
/*
<span style="color: #000000;background-color: #ffdddd">- * If the the new sample and the current sample are both valid
</span><span style="color: #000000;background-color: #ddffdd">+ * If the new sample and the current sample are both valid
</span> * and the difference between their offsets exceeds CLOCK_SGATE
* (3) times the jitter and the interval between them is less
* than twice the host poll interval, consider the new sample
</code></pre>
<br>
</li>
<li id='diff-18'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-18'>
<strong>
ntpd/refclock_arc.c
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/ntpd/refclock_arc.c
</span><span style="color: #000000;background-color: #ddffdd">+++ b/ntpd/refclock_arc.c
</span><span style="color: #aaaaaa">@@ -152,7 +152,7 @@ GENERAL
</span> significant.
c) Note that the bit time of 3.3ms adds to the potential error in
<span style="color: #000000;background-color: #ffdddd">- the the clock timestamp, since the bit clock of the serial link
</span><span style="color: #000000;background-color: #ddffdd">+ the clock timestamp, since the bit clock of the serial link
</span> may effectively be free-running with respect to the host clock
and the MSF clock. Actually, the error is probably 1/16th of
the above, since the input data is probably sampled at at least
</code></pre>
<br>
</li>
<li id='diff-19'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-19'>
<strong>
ntpd/refclock_mx4200.c
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/ntpd/refclock_mx4200.c
</span><span style="color: #000000;background-color: #ddffdd">+++ b/ntpd/refclock_mx4200.c
</span><span style="color: #aaaaaa">@@ -1064,7 +1064,7 @@ static int day1tab[] = {31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31};
</span> static int day2tab[] = {31, 29, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31};
/*
<span style="color: #000000;background-color: #ffdddd">- * Calculate the the Julian Day
</span><span style="color: #000000;background-color: #ddffdd">+ * Calculate the Julian Day
</span> */
static int
mx4200_jday(
</code></pre>
<br>
</li>
<li id='diff-20'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-20'>
<strong>
ntpd/refclock_oncore.c
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/ntpd/refclock_oncore.c
</span><span style="color: #000000;background-color: #ddffdd">+++ b/ntpd/refclock_oncore.c
</span><span style="color: #aaaaaa">@@ -420,7 +420,7 @@ struct refclock refclock_oncore = {
</span>
/*
* Understanding the next bit here is not easy unless you have a manual
<span style="color: #000000;background-color: #ffdddd">- * for the the various Oncore Models.
</span><span style="color: #000000;background-color: #ddffdd">+ * for the various Oncore Models.
</span> */
static struct msg_desc {
</code></pre>
<br>
</li>
<li id='diff-21'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec#diff-21'>
<strong>
util/calc_tickadj/calc_tickadj.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/util/calc_tickadj/calc_tickadj.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/util/calc_tickadj/calc_tickadj.txt
</span><span style="color: #aaaaaa">@@ -31,7 +31,7 @@ instead of slowing the clock down a little.
</span> If 'tick' on that box is 10,000,000 then by setting it to 9999779 the
drift value will be somewhere around 0.0.
<span style="color: #000000;background-color: #ffdddd">-_calc_tickadj_ tries to determine the the tick value by using the
</span><span style="color: #000000;background-color: #ddffdd">+_calc_tickadj_ tries to determine the tick value by using the
</span> _tickadj_ program from the {project-shortname} package. If this
doesn't work you can specify current tick manually on command line.
</code></pre>
<br>
</li>
</div>
<div class='footer' style='margin-top: 10px;'>
<p>
—
<br>
<a href="https://gitlab.com/NTPsec/ntpsec/compare/73f252f1a5e7e840d2a7f346d0a8e6191bb2a814...f723fcb4922d88591676743a0742bf16652a6cec">View it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can adjust your notification settings.
</p>
</div>
</body>
</html>