bk commit(7.3ce) BitKeeper User's Manual bk commit(7.3ce) NAME bk commit - commit deltas to a changeset SYNOPSIS bk commit [-cfq] [-l<file>] [--tag=tag<>] [-sALIAS<>] [-S] [-Y<file>] [-] bk commit [-cfq] [-l<file>] [-y<comment>] [-] DESCRIPTION This command commits work to a changeset, creating a logical group of changes which can span multiple files and/or multiple deltas within one or more files. If the command line does not have a trailing dash then bk commit will search the repository for any files which are in "pending" state, i.e., have deltas which do not yet belong to a changeset, and groups all of them into a changeset. If the trailing dash is present, then the com- mand takes the list of files to commit from the standard input; each line of input must be of the format: <sfile>|<rev> where <sfile> is an sfile name as described in bk filetypes and <rev> is a file revision number, such as 1.1 or 1.2. Example: SCCS/s.foo|1.2. This is the same format produced by "bk gfiles -pA" and "bk gfiles -pC". Note: <rev> specifies the most recent change to commit; all uncommitted changes prior to <rev> are also included. You can see what will be added to a changeset when you commit by run- ning: $ bk pending All revisions which you have checked in will become part of a change- set. As part of the commit step, you will be prompted for comments (if none were provided on the command line). The comments should describe the logical change that you have made; these comments are what will be displayed by bk changes. If no comments are provided and there is a BitKeeper/templates/commit file present in the repository, then the default comments are the con- tents of that file. Note: using bk citool is the preferred way to commit. Not only will bk citool help with checking in files, it will also create a changeset if you enter ChangeSet comments. Note: using the default comments on an import is not advisable. The default comments contain information about each file and can create very large comment entries in the ChangeSet file. The ChangeSet file is the center of activity in BitKeeper, and having an unnecessarily large one will not help performance. OPTIONS -c Use comments saved by a previous run of citool, fix, col- lapse, etc. It is an error if there are no saved com- ments. --ci Check in any edited files as part of the commit. -f Don't run interactively; do the commit with the default comments. Ignores the commit template, if any. -l<file> Get the list of files to commit from <file>. Each line of this file must use the <sfile>|<rev> format described above. -q Run quietly. -sALIAS Commit all pending files in the given aliases as well as the PRODUCT. Use -sPRODUCT if the top level commit is not wanted. -S --standalone Commit only in the current repository. --tag=<tag> Tag the tree with <tag> at the same time as the commit. -Y<file> Get check-in comment for changeset from <file>. -y<comment> Set check-in comment of changeset to <comment>. SEE ALSO bk changes bk citool bk import bk pending bk gfiles bk status bk tag bk templates CATEGORY Repository BitKeeper Inc 1E1 bk commit(7.3ce)