Lines Matching refs:example

89 example for proper handling of binary files, compression, and
125 operation (where possible).  For example, implementations have no choice
285 @example
302 @end example
345 An example session, and some further observations:
357 @example
359 @end example
376 @var{options} signifies the keyword expansion options (for example
389 @example
391 @end example
424 names in filenames, and any use of other conventions (for example,
473 In various contexts, for example the @code{Argument} request and the
475 string.  Often this will have been supplied by the user (for example,
493 @example
496 @end example
602 Here is an example of where a client gets @var{repository} and
605 @example
607 @end example
613 @example
624 @end example
626 In this example the response shown is @code{Clear-sticky}, but it could
631 @code{Directory} request.  For example, a subsequent @code{update}
634 @example
639 @end example
649 example, in response to an explicit user request).  While it is true
652 the various @code{Directory} requests for a single command (for example,
661 Here's a more complex example, in which we request an update of a
665 @example
679 @end example
688 The above example will work correctly in @sc{cvs} 1.10.1 and later.  The
697 Therefore, the above example would succeed in updating @code{dir1} and
703 @example
720 @end example
729 must be sent first.  For example, the following would not work to update
732 @example
742 @end example
747 its parent to mark it for recursion.  In the above example, at the time
758 needed.  For example, if the client is planning to use a
815 request (for example @samp{-kb} for a binary file).  This is similar to
826 timezone as appropriate.  An example of this format is:
828 @example
830 @end example
835 it (this means that the time might be in the future, for example).
909 @example
912 @end example
939 and instead connecting to the server when it is convenient (for example,
943 together with a @code{noop} request, for example), unless perhaps if
961 always use that case regardless of what the user specifies.  For example
976 a map for communicating with the server.  For example, suppose the server sends
1079 necessarily tell you all the files contained in a module, for example.
1084 For example, suppose that the server has a module defined by
1086 @example
1088 @end example
1108 @example
1117 @end example
1262 @code{Directory} and @code{Argument} requests.  For example:
1264 @example
1275 @end example
1284 request.  For example:
1286 @example
1302 @end example
1398 This is only a hint to the server.  It may still decide (for example, in
1478 For example, for a file @file{i386.mh}
1482 @example
1485 @end example
1495 @c FIXME: Need example here of how "repository" needs to be sent for
1570 @code{Modified}, or @code{Unchanged} was sent (for example, a file which
1574 distinguish files.  For example, the client is case-insensitive and the
1597 @code{Merged} it will send a @code{Copy-file} response.  For example, if
1643 convert that to their own timezone as appropriate.  An example of this
1646 @example
1648 @end example
1653 it (this means that the time might be in the future, for example).
1746 argument to a @code{co} request (for example, if the modules file
1753 example, @samp{*.exe}.  The @var{option} is @samp{b} for binary, and so
1766 server and the example output given in this document is just that,
1767 example output.  Servers are encouraged to use the @samp{MT} response,
1814 tags should be nested (for example one could have tags in the
1825 Here is an example of some tagged text responses.  Note that there is
1830 @example
1846 @end example
1851 @example
1856 @end example
1901 @example
1905 @end example
1918 @example
1925 @end example
1937 Here is an example; lines are prefixed by @samp{C: } to indicate the
1949 @example
1956 @end example
1966 @example
1971 @end example
1976 @example
1979 @end example
1987 @example
1993 @end example
1995 The server replies with the requested files.  In this example, there is
2001 @example
2015 @end example
2025 @example
2031 @end example
2043 @example
2051 @end example
2056 @example
2058 @end example
2062 @example
2072 @end example
2146 requests.  For example, perhaps all future requests should be a single
2168 portable from one system to another.  For example, a with a circle on