--- a/ChangeLog	Sun Jan 08 22:10:58 2017 -0800
+++ b/ChangeLog	Mon Jan 09 11:49:35 2017 -0800
@@ -1,3 +1,10 @@
+2017-01-09  Paul Eggert  <eggert@cs.ucla.edu>
+
+	maint: remove stray .texi files
+	Although these were superseded by other files like
+	doc/posix-functions/ctime.texi, the old files were not removed.
+	* doc/ctime.texi, doc/inet_ntoa.texi: Remove.
+
 2017-01-08  Paul Eggert  <eggert@cs.ucla.edu>
 
 	getprogname: fix port to IRIX

--- a/doc/ctime.texi	Sun Jan 08 22:10:58 2017 -0800
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,30 +0,0 @@
-@node ctime
-@section ctime
-@findex ctime
-
-@c Copyright (C) 2005, 2009-2017 Free Software Foundation, Inc.
-
-@c Permission is granted to copy, distribute and/or modify this document
-@c under the terms of the GNU Free Documentation License, Version 1.3 or
-@c any later version published by the Free Software Foundation; with no
-@c Invariant Sections, no Front-Cover Texts, and no Back-Cover
-@c Texts.  A copy of the license is included in the ``GNU Free
-@c Documentation License'' file as part of this distribution.
-
-The @code{ctime} function need not be reentrant, and consequently is
-not required to be thread safe.  Implementations of @code{ctime}
-typically write the time stamp into static buffer.  If two threads
-call @code{ctime} at roughly the same time, you might end up with the
-wrong date in one of the threads, or some undefined string.  There is
-a re-entrant interface @code{ctime_r}, that take a pre-allocated
-buffer and length of the buffer, and return @code{NULL} on errors.
-The input buffer should be at least 26 bytes in size.  The output
-string is locale-independent.  However, years can have more than 4
-digits if @code{time_t} is sufficiently wide, so the length of the
-required output buffer is not easy to determine.  Increasing the
-buffer size when @code{ctime_r} return @code{NULL} is not necessarily
-sufficient. The @code{NULL} return value could mean some other error
-condition, which will not go away by increasing the buffer size.
-
-A more flexible function is @code{strftime}.  However, note that it is
-locale dependent.

--- a/doc/inet_ntoa.texi	Sun Jan 08 22:10:58 2017 -0800
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,22 +0,0 @@
-@node inet_ntoa
-@section inet_ntoa
-@findex inet_ntoa
-
-@c Copyright (C) 2005, 2009-2017 Free Software Foundation, Inc.
-
-@c Permission is granted to copy, distribute and/or modify this document
-@c under the terms of the GNU Free Documentation License, Version 1.3 or
-@c any later version published by the Free Software Foundation; with no
-@c Invariant Sections, no Front-Cover Texts, and no Back-Cover
-@c Texts.  A copy of the license is included in the ``GNU Free
-@c Documentation License'' file as part of this distribution.
-
-The @code{inet_ntoa} function need not be reentrant, and consequently
-is not required to be thread safe.  Implementations of
-@code{inet_ntoa} typically write the time stamp into static buffer.
-If two threads call @code{inet_ntoa} at roughly the same time, you
-might end up with the wrong date in one of the threads, or some
-undefined string.  Further, @code{inet_ntoa} is specific for
-IPv4 addresses.
-
-A protocol independent function is @code{inet_ntop}.