NAME
bk edit − check out a file for editing
SYNOPSIS
bk edit [−q] [−rrev]
[file ... | −]
DESCRIPTION
If a file is not locked for writing, i.e., it is not visible
in a directory listing or it is read-only, then use bk
edit to check out the file and lock it, making it
available for writing.
bk edit with no options will check out all files in a directory.
OPTIONS
−q run quietly
−rrev Edit the file, rolling it back to the
contents specified by rev. (Or key or changeset
revision. See bk help terms under “rev
argument”) BitKeeper will check out the tip revision
combined with a set of include and exclude deltas needed to
produce the requested revision.
NOTES
While it may seem like this step could be done with a
simple
$ chmod +w foo.c
that is not correct. The reason is keyword expansion. Keywords are expanded only in read-only files, they are unexpanded in locked files. For example, if a file contains %M% %I%, when it is not locked that will look like foo.c 1.2. If the file is modified after the chmod then the keywords will forever more be foo.c 1.2, which is not likely to be the desired result. One could argue that BitKeeper should try and catch this case (and it does, bk check will frequently fix it), but it is impossible to do so correctly in all cases.
SEE ALSO
bk-terms
CATEGORY
File
Common