Lines Matching +full:working +full:- +full:directory

5 rcsintro \- introduction to RCS commands
35 check-in, and a log message summarizing the change.
73 If you have not already done so, make an RCS directory with the command
77 Then invoke the check-in command
83 directory,
90 should be a synopsis of the contents of the file.  All later check-in
94 Files in the RCS directory are called RCS files;
95 the others are called working files.
96 To get back the working file
98 in the previous example, use the check-out
111 .B "co  \-l  f.c"
121 tells you the difference between the most recently checked-in version
122 and the working file.
137 Of course, it is too late now to do the check-out with locking, because
138 another check-out would
141 .B "rcs  \-l  f.c"
152 .I "check-in"
159 the owner of the RCS file need not have a lock for check-in; all others
164 If you don't want to clutter your working directory with RCS files, create
167 in your working directory, and move all your RCS
168 files there.  RCS commands will look first into that directory to find
171 (Actually, pairs of RCS and working files can be specified in three ways:
172 (a) both are given, (b) only the working file is given, (c) only the
173 RCS file is given.  Both RCS and working files may have arbitrary path prefixes;
176 To avoid the deletion of the working file during check-in (in case you want to
184 check-out.  The first form also locks the checked in revision, the second one
185 doesn't.  Thus, these options save you one check-out operation.
188 Both update the identification markers in your working file (see below).
222 .B "ci  \-r1.3.1  f.c"
240 always see with which revision you are working.
261 the log messages that are requested during check-in.
282 7 (July 1985), 637-654.