From: Paul Eggert <eggert@cs.ucla.edu>
Date: Mon, 14 Aug 2006 22:56:17 +0000 (+0000)
Subject: OpenBSD -> Open@acronym{BSD}
X-Git-Tag: AUTOCONF-2.60a~18
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=bf41565f6b91c003aaa68db102b0fb78c1c1e8ae;p=thirdparty%2Fautoconf.git

OpenBSD -> Open@acronym{BSD}
---

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index a0ca35fe0..fa64191f6 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -13676,10 +13676,11 @@ subsequent label name.
 If a sed script is specified on the command line and ends in an
 @samp{a}, @samp{c}, or @samp{i} command, the last line of inserted text
 should be followed by a newline.  Otherwise some @command{sed}
-implementations (e.g., OpenBSD 3.9) do not append a newline to the
+implementations (e.g., Open@acronym{BSD} 3.9) do not append a newline to the
 inserted text.
 
-Many @command{sed} implementations (e.g., MacOS X 10.4, OpenBSD 3.9, Solaris 10
+Many @command{sed} implementations (e.g., MacOS X 10.4,
+Open@acronym{BSD} 3.9, Solaris 10
 @command{/usr/ucb/sed}) strip leading white space from the text of
 @samp{a}, @samp{c}, and @samp{i} commands.  Prepend a backslash to
 work around this incompatibility with Posix: