Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ci(1rcs)

co(1rcs)

ident(1rcs)

make(1)

rcs(1rcs)

rlog(1rcs)

rcsfile(5rcs)



RCSIN(1RCS)             COMMAND REFERENCE             RCSIN(1RCS)



NAME
     rcsin - see whether RCS files are checked in or not

SYNOPSIS
     rcsin [ -d path ] [ -p path ] [ -s ] [ -v ] [ file ...  ]

DESCRIPTION
     If any file specified is a working file with a locked RCS
     file, rcsin prints to standard output the name of the
     working file.  If file is an RCS file with a writable
     working file, rcsin prints the same information. If rcsin
     prints any messages, it also exits with a nonzero status.

     File can be the name of either an RCS file (ending in ,v) or
     a working file -- rcsin derives one name from the other.  If
     file is omitted, all RCS files in the current directory and
     the RCS subdirectory are examined (for example, *,v
     RCS/*,v).  By using the -d and -p options, the directories
     to be searched can be set.  This is useful in cases where
     RCS files are being obtained from various directories.

     Rcsin is often used within makefiles to assure that all
     work-in-progress is checked in.  It can be used to make sure
     that writable working files are not deleted by make.

OPTIONS
     -dpath
        Directory. In addition to searching .  and ./RCS , rcsin
        looks in the directories listed in path for the RCS file
        (*,v).  Path can be the name of one directory or a list
        of directories separated by whitespace.

     -ppath
        Path.  Rcsin searches the directories in path for the RCS
        file.  Path can be the name of one directory or a list of
        directories separated by whitespace.

     -s Silent.  No messages are written to standard-out; only an
        exit status is returned.

     -v Verbose.  Rcsin prints the reason file is not checked in
        (for example, "is writable" or "is locked") and, in the
        case of a locked file, either prints the version number
        and locker for each locked revision or prints the fact
        that the RCS lock file ( ,*, ) exists.

EXAMPLES
     The following example checks to see if the file foo.d is
     checked out.  If not, rcsin returns 0.  If it is checked
     out, rcsin tells you why (it is either a writable file or
     checked out).




Printed 4/6/89                                                  1





RCSIN(1RCS)             COMMAND REFERENCE             RCSIN(1RCS)



          rcsin -v foo.d

DIAGNOSTICS
     Exit status is 0 if all went well, 1 if any file is locked
     or any associated working files are writable, and 2 if some
     other error occurred.

CAVEATS
     If you use -p and -d together, the order of the arguments
     determines the results. The -p option removes whatever was
     in the search path, while -d appends to whatever was in the
     search path.

     The path argument to the -d and -p options contains
     directory names separated by whitespace.  This means that a
     directory name containing whitespace can not be used with
     these options.

SEE ALSO
     ci(1rcs), co(1rcs), ident(1rcs), make(1), rcs(1rcs),
     rlog(1rcs), and rcsfile(5rcs).


































Printed 4/6/89                                                  2



%%index%%
na:336,103;
sy:439,307;
de:746,1446;
op:2192,1225;
ex:3417,448;4273,26;
di:4299,287;
ca:4586,623;
se:5209,308;
%%index%%000000000144

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026