Here's some more.
Best regards,
Adrian
doc/ChangeLog addition:
2001-07-07 Adrian Aichner <[EMAIL PROTECTED]>
* ChangeLog: Fix typos.
* cvs.texinfo: Ditto.
* cvsclient.texi: Ditto.
cvs Patch (cvs -f -z3 diff -u):
cvs server: Diffing .
cvs server: Diffing contrib
cvs server: Diffing contrib/elib
cvs server: Diffing diff
cvs server: Diffing doc
Index: doc/ChangeLog
===================================================================
RCS file: /cvsroot/ccvs/doc/ChangeLog,v
retrieving revision 1.681
diff -u -r1.681 ChangeLog
--- doc/ChangeLog 6 Jul 2001 17:39:32 -0000 1.681
+++ doc/ChangeLog 7 Jul 2001 09:45:41 -0000
@@ -37,8 +37,8 @@
2001-06-22 Derek Price <[EMAIL PROTECTED]>
- * cvs.texinfo (checkout options): Fix transliteration typo in co
- example.
+ * cvs.texinfo (checkout options): Fix transposition typo in co
+ example.
(Patch from Adrian Aichner <[EMAIL PROTECTED]>.)
2001-06-12 Larry Jones <[EMAIL PROTECTED]>
Index: doc/cvs.texinfo
===================================================================
RCS file: /cvsroot/ccvs/doc/cvs.texinfo,v
retrieving revision 1.527
diff -u -r1.527 cvs.texinfo
--- doc/cvs.texinfo 6 Jul 2001 17:39:32 -0000 1.527
+++ doc/cvs.texinfo 7 Jul 2001 09:45:51 -0000
@@ -1284,7 +1284,7 @@
user-visible behavior, see @ref{Concurrency}. The
following section is aimed at people who are writing
tools which want to access a @sc{cvs} repository without
-interfering with other tools acessing the same
+interfering with other tools accessing the same
repository. If you find yourself confused by concepts
described here, like @dfn{read lock}, @dfn{write lock},
and @dfn{deadlock}, you might consult the literature on
@@ -2295,7 +2295,7 @@
connection on the right port. By default, the port
number is 2401; it would be different if your client
were compiled with @code{CVS_AUTH_PORT} defined to
-something else, though. This can also be sepcified in the CVSROOT variable
+something else, though. This can also be specified in the CVSROOT variable
(@pxref{Remote repositories}) or overridden with the CVS_CLIENT_PORT
environment variable (@pxref{Environment variables}).
@@ -4445,7 +4445,7 @@
The exception to this rule occurs when
a static tag has been attached to a dead revision manually. Use the branch tag
to merge all changes from the branch or use two static tags as merge endpoints
-to be sure that all intended changes are propogated in the merge.
+to be sure that all intended changes are propagated in the merge.
@c - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
@node Merging and keywords
@@ -11111,7 +11111,7 @@
Create a branch named @var{tag}. See @ref{Branching and merging}.
@item -B
-Used in conjuntion with -F or -d, enables movement and deletion of
+Used in conjunction with -F or -d, enables movement and deletion of
branch tags. Use with extreme caution.
@item -D @var{date}
Index: doc/cvsclient.texi
===================================================================
RCS file: /cvsroot/ccvs/doc/cvsclient.texi,v
retrieving revision 1.129
diff -u -r1.129 cvsclient.texi
--- doc/cvsclient.texi 28 Jun 2001 17:57:43 -0000 1.129
+++ doc/cvsclient.texi 7 Jul 2001 09:45:53 -0000
@@ -35,8 +35,8 @@
information about who modified them and when, and so on. People who
wish to look at or modify those files, known as @dfn{developers}, use
CVS to @dfn{check out} a @dfn{working directory} from the repository, to
-@dfn{check in} new versions of files to the repository, and other
-operations such as viewing the modification history of a file. If
+@dfn{check in} new versions of files to the repository, and to perform
+other operations such as viewing the modification history of a file. If
developers are connected to the repository by a network, particularly a
slow or flaky one, the most efficient way to use the network is with the
CVS-specific protocol described in this document.
@@ -82,14 +82,14 @@
@item
Providing a reliable transport is outside this protocol. The protocol
expects a reliable transport that is transparent (that is, there is no
-translation of characters, including characters such as such as
-linefeeds or carriage returns), and can transmit all 256 octets (for
-example for proper handling of binary files, compression, and
-encryption). The encoding of characters specified by the protocol (the
-names of requests and so on) is the invariant ISO 646 character set (a
-subset of most popular character sets including ASCII and others). For
-more details on running the protocol over the TCP reliable transport,
-see @ref{Connection and Authentication}.
+translation of characters, including characters such as linefeeds or
+carriage returns), and can transmit all 256 octets (for example for
+proper handling of binary files, compression, and encryption). The
+encoding of characters specified by the protocol (the names of requests
+and so on) is the invariant ISO 646 character set (a subset of most
+popular character sets including ASCII and others). For more details
+on running the protocol over the TCP reliable transport, see
+@ref{Connection and Authentication}.
@item
Security and authentication are handled outside this protocol (but see
@@ -205,7 +205,7 @@
@samp{E} and/or @samp{error}.
@item E @var{text}
-Provide a message for the user. After this reponse, the authentication
+Provide a message for the user. After this response, the authentication
protocol continues with another response. Typically the server will
provide a series of @samp{E} responses followed by @samp{error}.
Compatibility note: @sc{cvs} 1.9.10 and older clients will print
@@ -550,7 +550,7 @@
@item Valid-responses @var{request-list} \n
Response expected: no.
Tell the server what responses the client will accept.
-request-list is a space separated list of tokens.
+request-list is a space-separated list of tokens.
The @code{Root} request need not have been previously sent.
@item valid-requests \n
@@ -880,6 +880,7 @@
The @var{filename} is a file within the most recent directory sent with
@code{Directory}; it must not contain @samp{/}.
Additional data:
+@c APA: what about additional date?
@example
@var{notification-type} \t @var{time} \t @var{clienthost} \t
@var{working-dir} \t @var{watches} \n
@@ -1373,7 +1374,7 @@
@c lame terms (mostly because they are so awkward). Any better ideas?
The responses @code{Checked-in}, @code{New-entry}, @code{Updated},
@code{Created}, @code{Update-existing}, @code{Merged}, and
-@code{Patched} are refered to as @dfn{file updating} responses, because
+@code{Patched} are referred to as @dfn{file updating} responses, because
they change the status of a file in the working directory in some way.
The responses @code{Mode}, @code{Mod-time}, and @code{Checksum} are
referred to as @dfn{file update modifying} responses because they modify
@@ -1837,7 +1838,7 @@
@c line breaks. Any better solutions?
@c Other than that, this exchange is taken verbatim from the data
@c exchanged by CVS (as of Nov 1996). That is why some of the requests and
-@c reponses are not quite what you would pick for pedagogical purposes.
+@c responses are not quite what you would pick for pedagogical purposes.
@example
C: Root /u/cvsroot
cvs server: Diffing emx
cvs server: Diffing lib
cvs server: Diffing macintosh
cvs server: Diffing man
cvs server: Diffing os2
cvs server: Diffing src
cvs server: Diffing tools
cvs server: Diffing vms
cvs server: Diffing windows-NT
cvs server: Diffing windows-NT/SCC
cvs server: Diffing zlib
cvs server: Diffing zlib/amiga
cvs server: Diffing zlib/contrib
cvs server: Diffing zlib/contrib/asm386
cvs server: Diffing zlib/contrib/asm586
cvs server: Diffing zlib/contrib/asm686
cvs server: Diffing zlib/contrib/delphi
cvs server: Diffing zlib/contrib/delphi2
cvs server: Diffing zlib/contrib/iostream
cvs server: Diffing zlib/contrib/iostream2
cvs server: Diffing zlib/contrib/minizip
cvs server: Diffing zlib/contrib/untgz
cvs server: Diffing zlib/msdos
cvs server: Diffing zlib/nt
cvs server: Diffing zlib/os2
--
Adrian Aichner
mailto:[EMAIL PROTECTED]
http://www.xemacs.org/
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
