bcs(1) UNIX Programmer's Manual bcs(1)
NAME
bcs - manage branch revisions
SYNOPSIS
bcs [ -unlock] [bcs_options] [file_options] [rcs_options]
[file...]
bcs_options:
[ -auto -fast -debug -quiet -rc -sb -set -newset
-newconfig -path -newpath ]
file_options:
[ -all -wall -nowall -allb -wallb -nowallb -find
-wfind -nowfind]
rcs_options:
[ -o -u -l -c]
FLAGS
-unlock
Removes any lock established in the working sandbox.
bcs_options - Defaults may be modified and/or overridden with
the following switches.
-auto
Automatically choose the default answer to any question
asked by a command. If the default answer requires
manual intervention of some sort (e.g. to edit a file),
then revert to interactive mode for the duration of the
remaining operations for the current file and only
return to automatic mode after proceeding to the next
file in the list.
-fast
Always choose the default answer to any question asked
by a command. If the default answer requires manual
intervention of some sort (e.g. to edit a file), then
abort the operation on the current file instead and
proceed to the next file in the list.
-debug
Enable debugging code.
-quiet, -q
Be less verbose about actions taken.
-rc sandbox_rc_file
Specifies an alternate sandbox rc file. The defaults
is $HOME/.sandboxrc.
-sb sandbox_name
Name of the sandbox to use. If this option is not
Printed 1/23/91 4/25/90 1
bcs(1) UNIX Programmer's Manual bcs(1)
used, the sandbox will be determined by the environment
variable SANDBOX or, if that is not set, by the user's
default sandbox as specified in the sandbox rc file.
-sb_rc sandbox-rcfile
Provides the path and name of the sandbox's rc file to
use instaed of the default file sandbox/rc_files/local.
If this option is not used, the default sandbox rc file
will be used.
-set set_name
Performs operation on set_name instead of the current
default set.
-path path
Use path as the current directory within the shadow
source area. Used in conjunction with the -newpath
option.
-newpath
Create and/or update the ./.BCSpath-<user_set_name> to
contain the current relative path within the shadow
source area. This file is used by workon to chdir
within to the same subdirectory when working on a set
over an extended period of time.
file_options - These options cause the list of affected file
names supplied on the command line to be extended.
-all All files in the current set are operated on. If this
option is not chosen, the user must list the files to
use. The files in the set are listed in the sandbox's
source directory in the file .BCSset- user_setname.
-wall
The same as -all. but only operates on the files in the
set that are also writable.
-nowall
The same as -all. but only operates on the files in the
set that are not writable.
-alls user_set_name
The same as -all -set user_set_name.
-walls user_set_name
The same as -wall -set user_set_name.
-nowalls user_set_name
The same as -nowall -set user_set_name.
-find pattern
First use all files found recursively with find(1)
Printed 1/23/91 4/25/90 2
bcs(1) UNIX Programmer's Manual bcs(1)
beginning at the current directory that match pattern,
then use those on the command line.
-wfind pattern
The same as -find except use only writable files.
-nowfind pattern
The same as -find except use only non-writable files.
pattern (with any trailing ",v" suffix stripped from
all names), then use those on the command line.
rcs_options - A number of the regular RCS switches are also sup-
ported
-orange
outdates revisions given by range
-u[rev]
unlocks the revision with the number rev
-l[rev]
locks the revision with the number rev
-cstring
sets the comment leader to string
DESCRIPTION
This command acts as a front-end to the regular rcs command
and is a general purpose catch-all when branch maintenance
operations need not refer to any files,
The regular RCS -o option may be used to delete revisions,
but only by specifying the last component of the revision
number in the starting and ending revision places. The pre-
fix for the revision number is always implied by the current
branch name to protect against accidental removals of revi-
sions which belong to others.
The regular RCS -u option may be used to unlock a revision.
If no revision number is specified with the option, the
current branch name is assumed.
The regular RCS -l option may be used to lock a revision.
If no revision number is specified with the option, the
current branch name is assumed.
The regular RCS -c option may be used to change the comment
leader for a file.
FILES
~/.sandboxrc
Printed 1/23/91 4/25/90 3
bcs(1) UNIX Programmer's Manual bcs(1)
rc file that specifies default sandbox
rcfiles/sets
list of valid sets in sandbox
.BCSconfig-<user_set_name>
RCS configuration definition for branch (base direc-
tory)
.BCSpath-<user_set_name>
relative directory for branch within shadow area
.BCSset-<user_set_name>
list of files in branch (base directory)
.BCSlog-<user_set_name>
record of log messages for branch (base directory)
/tmp/b-$USER/*
temporary files
SEE ALSO
bci(1), bco(1), bcreate(1), bmerge(1), bdiff(1), bstat(1),
blog(1), rcs(1), rcsintro(1),
the RCS Cookbook.
Printed 1/23/91 4/25/90 4