bco(1) UNIX Programmer's Manual bco(1)
NAME
bco - check out branch revisions
SYNOPSIS
bco [ bcs_options ] [ file_options ] [ rcsco_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]
rcsco_options: [ -r -u ]
FLAGS
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
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.
Printed 1/23/91 4/25/90 1
bco(1) UNIX Programmer's Manual bco(1)
-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)
beginning at the current directory that match pattern,
then use those on the command line.
Printed 1/23/91 4/25/90 2
bco(1) UNIX Programmer's Manual bco(1)
-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.
rcsco_options - A number of the regular RCS switches are also
supported.
-rrev
retrieves the revison specified by rev.
-u leaves the resulting checked out revision unlocked
DESCRIPTION
The BCS commands implement a branch management facility
using the underlying set of regular RCS commands. Bco acts
as a front-end to the regular rcsco command.
Bco checks out the highest revision from each RCS file and
stores it into the corresponding working file. The working
file will be locked, unless -u has been specified.
The corresponding RCS file must already exist in the master
RCS area. If it does not then bcreate(1)R must be run to
create a new working file.
The regular RCS -r switch may be used to check-out a
specific revision. The regular RCS -j switch may be used to
specify a join with respect to the current branch or this
revision.
The checked-out revision is locked if it comes from the
current branch unless the -u switch is used. The check-out
operation is performed first to a temporary file if the
revision must be locked since it is not necessarily the case
that the owner of the master RCS area has write permission
within the base directory. At the successful completion of
each rcsco command, the working file is made writable unless
-u has been specified, and file is added to the .BCSset-
<branch-name> file if necessary. If the check-out operation
succeeds but does not produce a temporary working file (e.g.
the revision is marked "defunct"), then the working file is
deleted.
FILES
~/.sandboxrc
rc file that specifies default sandbox
Printed 1/23/91 4/25/90 3
bco(1) UNIX Programmer's Manual bco(1)
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
bcs(1), bci(1), bcreate(1), rcsco(1), rcs(1), rcsintro(1),
the RCS Cookbook.
Printed 1/23/91 4/25/90 4