Lines Matching refs:checked
180 checked out.
295 working directory was checked out.
367 directory (in ./CVS/Tag) and the checked-out files (on each line of
742 you checked out) is stored in CVS sub-directories, local to the user.
894 checked out on a branch, you will branch the branch. This
1124 be checked out together, built as one system or tagged as a consistent
1178 directory in the checked out working tree will match the "module" name
1195 "group1-Makefile" is checked out, the file named Makefile file will be
1196 found in a directory named $CVSROOT/group1 and will be checked out
1208 When checked out, a directory named "m1" appears in your current
1260 "unix" was checked out and built from the top down, using a set of
1262 checked out in /usr/local/src.
1451 - Keep a directory where the whole tree is checked out. (It might be
1457 "lndir" command) filled with links to the checked out files in the
2031 $CVSROOT/CVSROOT that should be checked out by mkmodules to provide a
2236 corresponding directory in every checked-out working directory. At the
2283 one on a file in the Attic, that file is checked out with the others.
2329 If you delete (or move) a directory, all checked-out versions of that
2331 checked-out directory and remove the matching working directory by
2534 ever checked out from the previous location of the Repository you just
2830 attached to the Vendor branch, causing revisions checked-in by "ci" to
2849 Though files checked in by RCS users will correctly cause
3229 You are in a directory checked out (or updated) with the '-A' option
3369 turned off for all checked out versions of the file.
3555 certain no one has the latest revision of the file checked out.
3601 CVS remembers what revisions you checked out and what branch you are
3634 retrieve any file you want within the checked-out directory. There is
3640 supply two pieces of naming information. While inside a checked-out
3674 sets of files are checked out together. It is the responsibility of
3680 7. Can I move a checked-out directory? Does CVS remember where it was
3681 checked out?
3690 When you move a checked-out directory, the CVS administrative files
3695 CVS remembers where you checked out the directory in the "history"
3844 you last checked out, committed or retrieved via "update") doesn't
4020 file into the Attic if you added it to a directory checked out on a
4044 revision (the revision last checked out, updated or committed):
4086 list) named "BASE" always refers to the revision you last checked out,
4097 checked in last Thursday?
4217 Displaying the checked-out modules and where they are being worked
4238 checked out. How do I fix it?
4242 your version of "release" doesn't have the '-f' option, or you checked
4296 used to tag the entire checked-out working tree when there is no
4302 9. "cvs history -a -o" only printed one line for each checked-out module.
4303 Shouldn't it print all the directories where the modules are checked out?
4309 cvs history -o What modules do I have checked out?
4316 The -o option chooses the "checked out modules" report, which is the
4400 at the head of a checked out working directory and at the head of the
4511 any working directories you checked out earlier.
4862 "commitinfo" log you set up might help to find checked out working
5147 delete the checked-out directory associated with the module name.
5168 3. Why can't I "release" portions of a checked out directory? I should be
5172 to keep track of which files in which directories are "checked out"
5179 were checked out because they are part of the same module or
5497 To add a symbolic label (a "tag") to the RCS files last checked out,
5527 "tag" places a tag on the BASE (i.e. last checked out, updated or
5834 At some time in the past you checked out or updated your directory
5843 Entries.Static, no files will be checked out that aren't already in
6409 last checked out or updated, type:
6517 To "tag" the BASE revisions (the ones you last checked out, updated,
6614 them occasionally? Is it OK to leave modules checked out?
6622 CVS doesn't care whether you leave modules checked out or not. The
6623 advantage of leaving them checked out is that you can quickly visit
6687 discrepancies exist between the files you originally checked out
6707 you can only "commit" to a file checked out with a sticky tag, if the
6778 8. How can I tell who has a module checked out?
6782 checkouts, who has them and where they were checked out. It is
6804 Revision 1.3 (What you originally checked out.)
7017 checked-in or in its original state. But CVS might have
7515 committed (via "update") since you checked out your working copy of
7600 branch or a checked out module. TeamWare allows you to manipulate
7837 A working file is a disk file containing a checked-out copy of a
7884 modules file for the checked-out module.]
7890 modules file for the checked-out module.]
7914 A "revision" is a version of a file that was "committed" ("checked
7952 "BASE" refers to the revision on the current branch you last checked
7992 A checked-out working directory, can be treated like a private branch.
8001 those who have checked-out the branch see the changes committed to
8069 the module name and the resulting path is checked out as in
8086 which, when checked out, creates an image of part of the
8090 The files checked out are exactly the same as the files
8096 which, when checked out, creates something you probably don't
8101 The file checked out is the same as what you would get if you
8149 Base: The revision you originally checked out. Later: A revision
8150 committed onto the current branch after you checked out the Base
8309 CVS does not dictate how to use disk space in the checked out working
8312 entire Repository to be checked out. That's simply bad planning.
8490 find lying on your system unless you have checked out their