<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>
Eric S. Raymond 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/f37b457efffe8ec1220fbc80416296b3f01783f1">f37b457e</a></strong>
<div>
<span>by Sanjeev Gupta</span>
<i>at 2016-01-23T12:35:48-05:00</i>
</div>
<pre class='commit-message'>Correct name of CC-BY License</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/719d1c0f1a94228ea663caa80f8f05acacf5a195">719d1c0f</a></strong>
<div>
<span>by Sanjeev Gupta</span>
<i>at 2016-01-23T12:35:48-05:00</i>
</div>
<pre class='commit-message'>Improve asciidoc markup</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/669098b7719be6466b7ab3de800b97bb9bdf9e5a">669098b7</a></strong>
<div>
<span>by Sanjeev Gupta</span>
<i>at 2016-01-23T12:35:48-05:00</i>
</div>
<pre class='commit-message'>Improve asciidoc markup and minor cleanup</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/dff6f1e08f017fddb3c8aae504c593dcbc10c299">dff6f1e0</a></strong>
<div>
<span>by Sanjeev Gupta</span>
<i>at 2016-01-23T12:35:48-05:00</i>
</div>
<pre class='commit-message'>Update known successful build targets, and reformat table for archs</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/fe72fc5f42fead028d043d6c23564e819800aeb1">fe72fc5f</a></strong>
<div>
<span>by Eric S. Raymond</span>
<i>at 2016-01-23T12:47:30-05:00</i>
</div>
<pre class='commit-message'>Remove unused image files.</pre>
</li>
</ul>
<h4>11 changed files:</h4>
<ul>
<li class='file-stats'>
<a href='#diff-0'>
devel/STATUS
</a>
</li>
<li class='file-stats'>
<a href='#diff-1'>
devel/TODO
</a>
</li>
<li class='file-stats'>
<a href='#diff-2'>
devel/hacking.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-3'>
<span class='deleted-file'>
−
docs/pic/alice31.gif
</span>
</a>
</li>
<li class='file-stats'>
<a href='#diff-4'>
<span class='deleted-file'>
−
docs/pic/driver43_1.gif
</span>
</a>
</li>
<li class='file-stats'>
<a href='#diff-5'>
<span class='deleted-file'>
−
docs/pic/driver43_2.jpg
</span>
</a>
</li>
<li class='file-stats'>
<a href='#diff-6'>
<span class='deleted-file'>
−
docs/pic/freq1211.gif
</span>
</a>
</li>
<li class='file-stats'>
<a href='#diff-7'>
<span class='deleted-file'>
−
docs/pic/group.gif
</span>
</a>
</li>
<li class='file-stats'>
<a href='#diff-8'>
<span class='deleted-file'>
−
docs/pic/offset1211.gif
</span>
</a>
</li>
<li class='file-stats'>
<a href='#diff-9'>
<span class='deleted-file'>
−
docs/pic/pzf509.jpg
</span>
</a>
</li>
<li class='file-stats'>
<a href='#diff-10'>
<span class='deleted-file'>
−
docs/pic/rabbit.gif
</span>
</a>
</li>
</ul>
<h4>Changes:</h4>
<li id='diff-0'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-0'>
<strong>
devel/STATUS
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/devel/STATUS
</span><span style="color: #000000;background-color: #ddffdd">+++ b/devel/STATUS
</span><span style="color: #aaaaaa">@@ -1,4 +1,4 @@
</span><span style="color: #000000;background-color: #ffdddd">-Last update, 2015 Dec 17
</span><span style="color: #000000;background-color: #ddffdd">+Last update, 2016 Jan 21
</span>
It builds on the following systems. In general there should be no warnings,
but as of the above date, there is one we can't easily work around. Some
<span style="color: #aaaaaa">@@ -6,10 +6,11 @@ compilers will complain about
</span> comparison between signed and unsigned integer expressions
at ntpd/ntp_io.c:4638
<span style="color: #000000;background-color: #ffdddd">-It's known to build cleanly on:
- Fedora 22 and 23 on i686 and x86_64
- Debian wheezy and jessie on amd64
- Ubuntu 14.04.3 LTS and 15.04 on x86_64
</span><span style="color: #000000;background-color: #ddffdd">+We have reports that it builds cleanly on at least:
+ Fedora 22 and 23 (i686, x86_64)
+ CentOS 5.11 (i386)
+ Debian wheezy (amd64) and jessie (amd64, i686)
+ Ubuntu 14.04.3 LTS and 15.10 on x86_64
</span> Raspbian wheezy and jessie on ARM v6 and v7 (Pi and Pi 2)
Debian wheezy on BeagleBone Black ARM v7
</code></pre>
<br>
</li>
<li id='diff-1'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-1'>
<strong>
devel/TODO
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/devel/TODO
</span><span style="color: #000000;background-color: #ddffdd">+++ b/devel/TODO
</span><span style="color: #aaaaaa">@@ -8,14 +8,14 @@
</span>
* Cleanup and separate features in pylib/*
<span style="color: #000000;background-color: #ffdddd">-* Add 'snapshot' feature to dump config status into a JSON file for collecting
</span><span style="color: #000000;background-color: #ddffdd">+* Add 'snapshot' feature to dump config status into a JSON file for collecting
</span> build + platform information
* The install production needs to warn of stale ntpdc and ntpdate binaries.
* Add support for enabling all conditional checks to ensure none are broken.
<span style="color: #000000;background-color: #ffdddd">-* Add support for disabling specific conditional tests to ensure nothing is
</span><span style="color: #000000;background-color: #ddffdd">+* Add support for disabling specific conditional tests to ensure nothing is
</span> compiled into the base in a surprising fashion, e.g. --undefine=FOO should
suppress generation of any FOO #define into config.h.
<span style="color: #aaaaaa">@@ -103,16 +103,18 @@
</span> read-only and solid. Maybe write a support package that does all the
work if you call it with the date/time.
<span style="color: #000000;background-color: #ffdddd">-Hal:
-> I think there is some interaction between when the ACTS driver calls and the
-> state of other stuff, like the connection to the net. This is probably a
-> good candidate to get cleaned up.
->
-> There is another possible tangle in this area. If you set "noselect" on the
-> server line in the config file, ntpd goes through all the action of
-> collecting the data and writing log files, but then drops the clock. I don't
-> know things well enough to be sure that this sort of logic won't pick one
-> back up.
</span><span style="color: #000000;background-color: #ddffdd">+[quote, Hal]
+__________
+I think there is some interaction between when the ACTS driver calls and the
+state of other stuff, like the connection to the net. This is probably a
+good candidate to get cleaned up.
+
+There is another possible tangle in this area. If you set "noselect" on the
+server line in the config file, ntpd goes through all the action of
+collecting the data and writing log files, but then drops the clock. I don't
+know things well enough to be sure that this sort of logic won't pick one
+back up.
+__________
</span>
* Forward-port NTP Classic fix for [Bug 2830] just in case we want to
revive Autokey someday.
</code></pre>
<br>
</li>
<li id='diff-2'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-2'>
<strong>
devel/hacking.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/devel/hacking.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/devel/hacking.txt
</span><span style="color: #aaaaaa">@@ -49,7 +49,7 @@ cause buffer overruns and (all too often) exploitable security holes:
</span> * sprintf, vsprintf: use snprintf and vsnprintf instead.
* In scanf and friends, the %s format without length limit is banned.
* strtok: use strtok_r() or unroll this into the obvious loop.
<span style="color: #000000;background-color: #ffdddd">-* gets: Use fgets instead.
</span><span style="color: #000000;background-color: #ddffdd">+* gets: Use fgets instead.
</span> * gmtime(), localtime(), asctime(), ctime(): use the reentrant *_r variants.
* tmpnam() - use mkstemp() or tmpfile() instead.
* dirname() - the Linux version is re-entrant but this property is not portable.
<span style="color: #aaaaaa">@@ -84,13 +84,14 @@ Such simplicity is often difficult or impractical for heterogenous
</span> data that needs to be both grouped and labeled, so we have another
convention for those cases. Here it is:
<span style="color: #000000;background-color: #ddffdd">+[quote]
</span> Wherever it is reasonable, tools that generate complex reports to
standard output should be able to emit two formats. The default can be
relatively unstructured multiline text for human eyeballs. There
should also be a -j/--json option that emits a self-describing JSON
<span style="color: #000000;background-color: #ffdddd">-object. You can read about JSON at
</span><span style="color: #000000;background-color: #ddffdd">+object.
</span>
<span style="color: #000000;background-color: #ffdddd">- http://www.json.org/
</span><span style="color: #000000;background-color: #ddffdd">+You can read about JSON at http://www.json.org/
</span>
Be aware that if you present a tool design with a messy output format
and no JSON option it is quite likely to be rejected.
<span style="color: #aaaaaa">@@ -104,8 +105,8 @@ always with full years and timezone offset.
</span>
Much of the historic code in this distribution is under the "NTP
License" resembling BSD-2-clause. Our favored licenses are
<span style="color: #000000;background-color: #ffdddd">-BSD-2-clause for code and Creative Commons Attribute 4.0 License for
-documentation.
</span><span style="color: #000000;background-color: #ddffdd">+BSD-2-clause for code and Creative Commons Attribution 4.0 License
+for documentation.
</span>
Please do *not* submit code under GPL or other licenses which place
conditions on derived works; we cannot accept such code.
<span style="color: #aaaaaa">@@ -250,9 +251,9 @@ The file "dot.emacs" has the emacs C-mode indentation style that Dave likes.
</span> === Other languages ===
The only scripting languages allowed and supported are POSIX sh and
<span style="color: #000000;background-color: #ffdddd">-Python 2.5. If you find code in the distribution that is in a
-scripting language and not one of these, you would be doing us a
-favor by translating it into Python or sh.
</span><span style="color: #000000;background-color: #ddffdd">+Python 2.5 or later, but not Python 3. If you find code in the
+distribution that is in a scripting language and not one of these,
+you would be doing us a favor by translating it into Python or sh.
</span>
The reason for this policy is not that we hate all other scripting
languages, it's to reduce the complexity of maintenance and testing
</code></pre>
<br>
</li>
<li id='diff-3'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-3'>
<strong>
docs/pic/alice31.gif
</strong>
deleted
</a>
<hr>
<pre class="highlight"><code>Binary files a/docs/pic/alice31.gif and /dev/null differ
</code></pre>
<br>
</li>
<li id='diff-4'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-4'>
<strong>
docs/pic/driver43_1.gif
</strong>
deleted
</a>
<hr>
<pre class="highlight"><code>Binary files a/docs/pic/driver43_1.gif and /dev/null differ
</code></pre>
<br>
</li>
<li id='diff-5'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-5'>
<strong>
docs/pic/driver43_2.jpg
</strong>
deleted
</a>
<hr>
<pre class="highlight"><code>Binary files a/docs/pic/driver43_2.jpg and /dev/null differ
</code></pre>
<br>
</li>
<li id='diff-6'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-6'>
<strong>
docs/pic/freq1211.gif
</strong>
deleted
</a>
<hr>
<pre class="highlight"><code>Binary files a/docs/pic/freq1211.gif and /dev/null differ
</code></pre>
<br>
</li>
<li id='diff-7'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-7'>
<strong>
docs/pic/group.gif
</strong>
deleted
</a>
<hr>
<pre class="highlight"><code>Binary files a/docs/pic/group.gif and /dev/null differ
</code></pre>
<br>
</li>
<li id='diff-8'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-8'>
<strong>
docs/pic/offset1211.gif
</strong>
deleted
</a>
<hr>
<pre class="highlight"><code>Binary files a/docs/pic/offset1211.gif and /dev/null differ
</code></pre>
<br>
</li>
<li id='diff-9'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-9'>
<strong>
docs/pic/pzf509.jpg
</strong>
deleted
</a>
<hr>
<pre class="highlight"><code>Binary files a/docs/pic/pzf509.jpg and /dev/null differ
</code></pre>
<br>
</li>
<li id='diff-10'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1#diff-10'>
<strong>
docs/pic/rabbit.gif
</strong>
deleted
</a>
<hr>
<pre class="highlight"><code>Binary files a/docs/pic/rabbit.gif and /dev/null differ
</code></pre>
<br>
</li>
</div>
<div class='footer' style='margin-top: 10px;'>
<p>
—
<br>
<a href="https://gitlab.com/NTPsec/ntpsec/compare/2b6e2e0413d219ee1f2a22ae1f1a7286f93d7c73...fe72fc5f42fead028d043d6c23564e819800aeb1">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>