URI: 
       tman9: rename IM to MR - plan9port - [fork] Plan 9 from user space
  HTML git clone git://src.adamsgaard.dk/plan9port
   DIR Log
   DIR Files
   DIR Refs
   DIR README
   DIR LICENSE
       ---
   DIR commit 36cd4c58c1346375b98f517fb8568be5bb47618d
   DIR parent 0144f87dc6c7f2f6becbd55519e433a9b36a466f
  HTML Author: Fazlul Shahriar <fshahriar@gmail.com>
       Date:   Fri, 29 Jan 2021 18:55:29 -0500
       
       man9: rename IM to MR
       
       Commit d32deab17bfffa5bffc5fab3e6577558e40888c5 renamed IM to MR but
       tthese man pages were missed.
       
       Diffstat:
         M man/man9/0intro.9p                  |      18 +++++++++---------
         M man/man9/attach.9p                  |       4 ++--
         M man/man9/clunk.9p                   |       2 +-
         M man/man9/flush.9p                   |       4 ++--
         M man/man9/open.9p                    |       4 ++--
         M man/man9/openfd.9p                  |       8 ++++----
         M man/man9/read.9p                    |       2 +-
         M man/man9/remove.9p                  |       2 +-
         M man/man9/stat.9p                    |       4 ++--
         M man/man9/version.9p                 |       2 +-
         M man/man9/walk.9p                    |       4 ++--
       
       11 files changed, 27 insertions(+), 27 deletions(-)
       ---
   DIR diff --git a/man/man9/0intro.9p b/man/man9/0intro.9p
       t@@ -21,7 +21,7 @@ such a machine is called, somewhat confusingly, a
        Another possibility for a server is to synthesize
        files on demand, perhaps based on information on data structures
        maintained in memory; the
       -.IM plumber (4)
       +.MR plumber (4)
        server is an example of such a server.
        .PP
        A
       t@@ -63,7 +63,7 @@ bytes of data.
        Text strings are represented this way,
        with the text itself stored as a UTF-8
        encoded sequence of Unicode characters (see
       -.IM utf (7) ).
       +.MR utf (7) ).
        Text strings in 9P messages are not
        .SM NUL\c
        -terminated:
       t@@ -114,7 +114,7 @@ Plan 9 names may contain any printable character (that is, any character
        outside hexadecimal 00-1F and 80-9F)
        except slash.)
        Messages are transported in byte form to allow for machine independence;
       -.IM fcall (3)
       +.MR fcall (3)
        describes routines that convert to and from this form into a machine-dependent
        C structure.
        .SH MESSAGES
       t@@ -348,7 +348,7 @@ a ``current file'' on the server.
        Fids are somewhat like file descriptors in a user process,
        but they are not restricted to files open for I/O:
        directories being examined, files being accessed by
       -.IM stat (3)
       +.MR stat (3)
        calls, and so on \(em all files being manipulated by the operating
        system \(em are identified by fids.
        Fids are chosen by the client.
       t@@ -461,7 +461,7 @@ to have their input or output attached to fids on 9P servers.
        See
        .IR openfd (9p)
        and
       -.IM 9pclient (3)
       +.MR 9pclient (3)
        for details.
        .PP
        The
       t@@ -475,7 +475,7 @@ access permissions (read, write and execute for owner, group and public),
        access and modification times, and
        owner and group identifications
        (see
       -.IM stat (3) ).
       +.MR stat (3) ).
        The owner and group identifications are textual names.
        The
        .B wstat
       t@@ -523,12 +523,12 @@ into 9P messages.
        .SS Unix
        On Unix, 9P services are posted as Unix domain sockets in a
        well-known directory (see
       -.IM getns (3)
       +.MR getns (3)
        and
       -.IM 9pserve (4) ).
       +.MR 9pserve (4) ).
        Clients connect to these servers using a 9P client library
        (see
       -.IM 9pclient (3) ).
       +.MR 9pclient (3) ).
        .SH DIRECTORIES
        Directories are created by
        .B create
   DIR diff --git a/man/man9/attach.9p b/man/man9/attach.9p
       t@@ -122,7 +122,7 @@ and
        and
        .I fsauth
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        generate
        .B attach
        and
       t@@ -163,6 +163,6 @@ transactions.
        .\" .B mount
        .\" system call on an uninitialized connection.
        .SH SEE ALSO
       -.IM 9pclient (3) ,
       +.MR 9pclient (3) ,
        .IR version (9P),
        Plan 9's \fIauthsrv\fR(6)
   DIR diff --git a/man/man9/clunk.9p b/man/man9/clunk.9p
       t@@ -41,7 +41,7 @@ generated by
        and
        .I fsunmount
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        and indirectly by other actions such as failed
        .I fsopen
        calls.
   DIR diff --git a/man/man9/flush.9p b/man/man9/flush.9p
       t@@ -99,11 +99,11 @@ flushing a
        and flushing an invalid tag.
        .SH ENTRY POINTS
        The
       -.IM 9pclient (3)
       +.MR 9pclient (3)
        library does not generate
        .B flush
        transactions..
       -.IM 9pserve (4)
       +.MR 9pserve (4)
        generates
        .B flush
        transactions to cancel transactions pending when a client hangs up.
   DIR diff --git a/man/man9/open.9p b/man/man9/open.9p
       t@@ -160,7 +160,7 @@ in this case, the
        .I fscreate
        call
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        uses
        .B open
        with truncation.
       t@@ -209,7 +209,7 @@ again.
        and
        .I fscreate
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        both generate
        .B open
        messages; only
   DIR diff --git a/man/man9/openfd.9p b/man/man9/openfd.9p
       t@@ -43,18 +43,18 @@ it cannot be
        .PP
        .I Openfd
        is implemented by
       -.IM 9pserve (4) .
       +.MR 9pserve (4) .
        9P servers that post their services using
       -.IM 9pserve (4)
       +.MR 9pserve (4)
        (or indirectly via
       -.IM post9pservice (3) )
       +.MR post9pservice (3) )
        will never see a
        .B Topenfd
        message.
        .SH ENTRY POINTS
        .I Fsopenfd
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        generates an
        .B openfd
        message.
   DIR diff --git a/man/man9/read.9p b/man/man9/read.9p
       t@@ -114,7 +114,7 @@ to be transferred atomically.
        and
        .I fswrite
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        generate the corresponding messages.
        Because they take an offset parameter, the
        .I fspread
   DIR diff --git a/man/man9/remove.9p b/man/man9/remove.9p
       t@@ -45,7 +45,7 @@ so other fids typically remain usable.
        .SH ENTRY POINTS
        .I Fsremove
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        generates
        .B remove
        messages.
   DIR diff --git a/man/man9/stat.9p b/man/man9/stat.9p
       t@@ -88,7 +88,7 @@ The
        and
        .I convD2M
        routines (see
       -.IM fcall (3) )
       +.MR fcall (3) )
        convert between directory entries and a C structure called a
        .BR Dir .
        .PP
       t@@ -263,7 +263,7 @@ messages are generated by
        and
        .IR fsdirstat
        (see
       -.IM 9pclient (3) ).
       +.MR 9pclient (3) ).
        .PP
        .B Wstat
        messages are generated by
   DIR diff --git a/man/man9/version.9p b/man/man9/version.9p
       t@@ -91,7 +91,7 @@ requests is called a
        .SH ENTRY POINTS
        .I Fsversion
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        generates
        .B version
        messages;
   DIR diff --git a/man/man9/walk.9p b/man/man9/walk.9p
       t@@ -149,13 +149,13 @@ may be packed in a single message.
        This constant is called
        .B MAXWELEM
        in
       -.IM fcall (3) .
       +.MR fcall (3) .
        Despite this restriction, the system imposes no limit on the number of elements in a file name,
        only the number that may be transmitted in a single message.
        .SH ENTRY POINTS
        .I Fswalk
        (see
       -.IM 9pclient (3) )
       +.MR 9pclient (3) )
        generates walk messages.
        One or more walk messages may be generated by
        any call that evaluates file names: