Requires: repository, sandbox.
Changes: nothing.
Synonyms:
This command queries the server for everyone editing a file or group of files. It can also optionally show which bugs are being worked on.
The server only knows the last reported state of each client. In a controlled environment this is very likely to be accurate, however it is possible to leave edits on the server and not on the client (for example my deleting the sandbox without using commit/unedit).
The normal editors output is as follows:
components.dir/TEST.xml tmh Fri Dec 3 16:15:00 2004 GMT tucker c:\temp\repos\components.dir rep/version_no.h tmh Thu Nov 4 17:37:43 2004 GMT tucker D:\t\test\rep
If you list edits for all branches and bug identifiers you get an extra columns. The full output is as follows:
components.dir/TEST.xml tmh Fri Dec 3 16:15:00 2004 GMT tucker c:\temp\repos\components.dir 3465 HEAD rep/version_no.h tmh Thu Nov 4 17:37:43 2004 GMT tucker D:\t\test\rep HEAD
The first output is designed to be compatible with older cvs versions that did not support the full cvsnt feature set.
Show all branches, not just the current branch.
Check whether edit on the selected files would actually succeed. This can be used by frontends to verify an edit without actually performing it.
Process this directory only
Process directories recursively (default).
Show active bugs within the output.