[Git][NTPsec/ntpsec][master] 3 commits: Fix spelling of "repetitions".

[Mark Atwood]

Mark Atwood pushed to branch master at NTPsec / ntpsec


Commits:
3cde2d60 by Matt Selsky at 2016-01-08T23:19:42-05:00
Fix spelling of "repetitions".

- - - - -
4a981580 by Matt Selsky at 2016-01-08T23:20:00-05:00
Clean up typos in documentation.

- - - - -
1baa4021 by Mark Atwood at 2016-01-19T07:42:30+00:00
Merge branch 'issue36' into 'master'

Fix issue 36



See merge request !2
- - - - -


3 changed files:

- devel/tour.txt
- ntpd/refclock_chu.c
- ntpd/refclock_parse.c


Changes:

=====================================
devel/tour.txt
=====================================
--- a/devel/tour.txt
+++ b/devel/tour.txt
@@ -38,8 +38,8 @@ calendar representations.
 
 The vint64 type is a historical relic.  NTP was written well before
 the 64-bit word size became common. While compilers on 32-bit machines
-sometimes had have have "long long" as an integral 64-bit type, this
-was not guaranteed before C99.
+sometimes have had "long long" as an integral 64-bit type, this was not
+guaranteed before C99.
 
 Thus, NTP carries a "variant 64-bit int" type that is actually a union
 with several different interpretations. Support is mainly in
@@ -86,7 +86,7 @@ These aren't local types themselves - both are standardized in
 ANSI/POSIX.  They're both second/subsecond pairs intended to represent
 time without loss of precision due to float operations.  The
 difference is that a timespec represents nanoseconds, while a timeval
-represents only nanonseconds.
+represents only microseconds.
 
 Historically, struct timeval is associated with the minicomputer-based
 Berkeley Unixes of the 1980s, designed when processor clocks were
@@ -120,7 +120,7 @@ waiting for a UDP packet to arrive on some set of open interfaces, or
 a clock sample to arrive from a locally-attached reference clock.
 Incoming packets and clock samples are fed to a protocol state
 machine, which may generate UDP sends to peers.  This main loop is
-capured by a function in ntpd/ntpd.c tellingly named 'mainloop()'.
+captured by a function in ntpd/ntpd.c tellingly named 'mainloop()'.
 
 This main loop is interrupted once per second by a timer tick that
 sets an alarm flag visible to the mainloop() logic.  When execution


=====================================
ntpd/refclock_chu.c
=====================================
--- a/ntpd/refclock_chu.c
+++ b/ntpd/refclock_chu.c
@@ -1210,7 +1210,7 @@ chu_a(
 
 	/*
 	 * Extract the second number; it must be in the range 2 through
-	 * 9 and the two repititions must be the same.
+	 * 9 and the two repetitions must be the same.
 	 */
 	temp = (up->cbuf[k + 4] >> 4) & 0xf;
 	if (temp < 2 || temp > 9 || k + 9 >= nchar || temp !=


=====================================
ntpd/refclock_parse.c
=====================================
--- a/ntpd/refclock_parse.c
+++ b/ntpd/refclock_parse.c
@@ -213,7 +213,7 @@ typedef struct bind
 
 struct errorregression
 {
-	u_long err_count;	/* number of repititions per class */
+	u_long err_count;	/* number of repetitions per class */
 	u_long err_delay;	/* minimum delay between messages */
 };
 
@@ -283,7 +283,7 @@ struct errorinfo
 {
 	u_long err_started;	/* begin time (ntp) of error condition */
 	u_long err_last;	/* last time (ntp) error occurred */
-	u_long err_cnt;	/* number of error repititions */
+	u_long err_cnt;	/* number of error repetitions */
 	u_long err_suppressed;	/* number of suppressed messages */
 	struct errorregression *err_stage; /* current error stage */
 };



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/fecbe68c35db3853ae06ba376e2ea03dee88e2ce...1baa4021cb30ab51f152b70ce7232666740d089e
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/vc/attachments/20160119/980713ce/attachment.html>