|
Modelling clouds and climate |
Status/revisions |
| Path: Contents > Other CVS Commands > Status/revisions | |
|
Site Map
Contents About CVS Terminology Using CVS (import) (checkout) (update/diff) (commit) (release) Other CVS Commands (log) (add/del) Spetial Topics References Web Contact: Phil Austin Site created with Cheetah. Last updated: Mar 13 2003 |
Statuscvs status Each file in a project has its own revision number. When a file is committed, the last portion of the revision number is incremented by one. Thus, at any given time, the various files comprising a project may have very different revision numbers. This just means that some files have been changed (committed) more often than others. You can usually ignore a file's revision number. In most situations, the numbers are just internal bookkeeping that CVS handles automatically. However, being able to find and compare revision numbers is extremely handy when you have to retrieve (or diff against) an earlier copy of a file. Examining the Entries file is on way to discover a revision number: $ cd myproj/CVS $ cat Entries /README.txt/1.1.1.1/Sun Apr 18 18:18:22 1999// /hello.c/1.2/Mon Apr 19 06:35:15 1999// D/a-subdir//// $ You can also use the status command:
paste$ cvs status hello.c
===================================================================
File: hello.c Status: Up-to-date
Working revision: 1.3 Tue Apr 20 02:34:42 1999
Repository revision: 1.3 /usr/local/cvs/myproj/hello.c,v
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
which, if invoked without any files being named, shows the status of every file in the project: paste$ cvs status |