Lines Matching refs:RCS
62 in an RCS file, so if someone does tamper, we can recover the database.
148 software vendor. It is implemented using a specific RCS branch
157 RCS concept with the same name. If you are using Vendor
161 - The RCS 1.1.1 branch.
171 that does not appear in any of the RCS files or the CVS control
176 same as the RCS "default branch". Normally the CVS default
184 attached to a real RCS branch. When you commit a file to a
185 magic branch, the branch becomes real (i.e. a physical RCS
191 How RCS uses the word "branch":
193 - The RCS "Main Branch" (Synonym: "The Trunk") contains a
198 - The RCS "Default" branch starts out attached to the RCS "Main
199 Branch". For RCS purposes, it can be changed to point to any
200 branch. Within CVS, you *must*not* alter the RCS default
202 and it must either point to the RCS Main Branch, or the Vendor
490 depends on your version of your RCS "merge" command (actually the "co
491 -j" option, which depends on the version of "diff3" you configured RCS
511 Merges can also be performed by handing RCS revisions to the '-j'
612 file. You can continue that way, making changes along the RCS Main
627 "tag -F -b" command was executed. CVS and RCS have no way of saving
672 opposed to the use of RCS branches to support some other scheme) is a
697 When CVS adds a branch tag, it attaches an RCS symbol to a
699 branch point as a prefix. (See Section 3O, on the "tag" command.) RCS
711 Because your command creates an RCS branch, not a CVS branch. See the
712 above discussion on branches. RCS branches are used to support CVS
714 direct control over the RCS files.
720 But you have to remember that you are using RCS commands on a CVS
732 idea of your "default branch", which has little to do with RCS's
862 You can avoid digging into RCS revision numbers (executing "update
977 20. How to I avoid merge collisions in the RCS $\Log$ data?
979 In short, you can't. The RCS $\Log$ keyword is handled differently
980 from all other RCS keywords.
1053 (RCS and diff, mainly) are fairly solid nowadays. They work.
1527 sources you want to put into it, plus a bit of overhead for the RCS
1535 You need some helper tools besides CVS such as "RCS" and a good set
1590 See 1B.4 If you use recent versions of RCS and "diff", you won't run
1601 RCS versions earlier than 5.5 print the above error when a file does
1608 The solution is to upgrade to RCS 5.5 or later. (Of course, this won't
1609 fix filesystem failures. It will merely allow RCS (and therefore CVS)
1614 2. Explain: "RCS file /Repository/module/file.c,v is in use"
1616 This is an RCS error that occurs when its internal lock file has been
1617 left around by an RCS command interrupted by some sort of system
1630 This is an error message from RCS Version 3 when it tries to read a
1631 file created by a later version of RCS.
1633 HP decided to "standardize" on an ancient version of RCS some time
1636 Since the error comes from having a later version of RCS than HP
1638 recently changed your $PATH or installed the HP package that has RCS
1642 proper versions of the RCS programs that CVS uses, or change your PATH
1644 RCS, you should upgrade. See 1B.4
1648 4. Explain: "error: RCS file name `xyz .c' contains white space"
1650 RCS 5.6 doesn't allow white space in filenames. Apparently this
1651 restriction will be removed in RCS 5.7, but CVS may still require that
1661 is no RCS file in the Repository to back it up.
1692 This is an RCS problem, since the ,<file>, syntax for file names is
1693 used by RCS and not CVS.
1695 RCS constructs a new <file>,v in a temporary file named ,<file>,
1701 system call, RCS runs uses an internal version of this algorithm to
1747 which is a port of CVS 1.3 (along with RCS and diff) and:
1771 You can share RCS files between Unix and DOS while avoiding the MS-DOS
1773 '-x/,v'. New RCS files will be created without the standard ",v"
1834 HP distributes RCS version 3 (a circa 1983 release!) with HP-UX. CVS
1835 does not work with RCS version 3; it requires RCS version 4 or later.
1836 Your best bet is to find the latest version of RCS and install it
1841 RCS to avoid mmap by setting has_mmap to 0 in RCS's conf.h. This bug
2030 checkoutlist contains a list of other files kept under RCS in
2038 that is not under RCS.
2045 Only in the RCS files. The Repository holds exactly two things: the
2046 tree of RCS files (each usually ending in ",v") and the CVSROOT
2066 You can move RCS files directly into the Repository.
2279 RCS file into a sub-directory named "Attic" within the Repository.
2307 the equivalent RCS command "rcs -o").
2352 11. Can I convert to CVS from RCS without losing my revision history?
2354 Yes, you can simply move (or copy) your RCS files into a directory
2359 12. Can I move RCS files with branches in them into the Repository?
2369 You can use other RCS branches under CVS. There is no need to create
2374 13. Can I use raw RCS commands on the Repository?
2378 to RCS revision histories) outside the CVSROOT directory.
2380 But using raw RCS commands to change branches, tags or other things
2383 See 4D.7 on RCS/CVS sharing of the Repository and Section 3B on the
2388 14. How do I convert from SCCS to RCS?
2391 directory) on every file. Then you can move the resulting RCS files
2439 Try to use the RCS access control lists, though I don't think CVS
2458 Non-RCS files. Other than the files CVS needs in the
2460 RCS file.
2462 Lock files (both CVS '#*' and RCS ',*' files) left around after
2467 Locked files. (RCS locks, that is.)
2499 Files that have a default RCS branch that is not 1.1.1 (From an
2558 This is a standard RCS action.
2561 Repository using CVS (or RCS) commands. You have to change the
2580 First of all, if you want to use binary files, you should get RCS 5.7
2582 bug fixes). Secondly, follow the instructions for installing RCS very
2598 "How can I lock files while I'm working on them the way RCS does?"
2607 2. Can I edit the RCS (",v") files in the Repository?
2609 Yes, but be very careful. The RCS files are not free-form files, they
2613 command, which can talk directly to RCS.
2615 Though no one actively encourages the editing of RCS files, many
2620 RCS 5.6 or later, you should use `cvs admin -m'.)
2664 that followed the earliest outdated revision using RCS (or "cvs
2668 You *can't* insert a revision into the current RCS file.
2712 file will cause CVS to construct an RCS branch named <X>.Y and check
2715 Note: TAG1 is *not* considered to be attached to <X> by RCS, which
2735 RCS file, moving it will make the existing branch in the file seem to
2737 want to forget the existence of those RCS branches.
2747 a different RCS branch number (<X>.Z instead of <X>.Y).
2780 a magic CVS branch tag, "admin" is a direct interface to RCS which
2781 sees a magic branch tag as a simple (though non-existent) RCS revision
2788 than CVS usually does. (Because they are coming directly from RCS.)
2796 6. Can I use RCS locally to record my changes without making them globally
2809 7. How can I allow access to the Repository by both CVS and RCS?
2813 and CVS makes certain operations *easier* than a series of RCS
2819 If you really must allow routine RCS access to the CVS Repository, you
2820 can link an RCS sub-directory into a piece of the Repository:
2822 ln -s /Repository/some/directory/I/want RCS
2824 and RCS will work just fine.
2826 Those who are using RCS will have to keep the following in mind:
2829 not been changed using CVS, the *RCS* default branch will remain
2832 moves the RCS default branch on first commit.
2836 branches. Then RCS will work OK.
2841 Normal RCS practice locks a file on checkout with "co -l". In such
2842 an environment, RCS users should plan to keep survival gear and food
2845 run the RCS users out of town with pitchforks and machetes.
2849 Though files checked in by RCS users will correctly cause
2854 RCS users will get no warning and will not be required to merge older
2861 RCS is great. I have used it for years. But I wouldn't mix it this
2871 CVS restores dates from the RCS files only on first "checkout". After
2878 execute "update". If CVS sets the date to the one in the RCS file, the
2903 to match the timestamp stored on the revision in the Repository's RCS
2946 course, if you catch a single file in the middle of RCS activity, you
2957 You could also use the RCS functions, "rlog" and "rcsdiff" to display
2960 You need RCS version 5 or later for the commands described above to
3102 bit set), you might have to modify CVS (or RCS) to reset the group
3335 in this file it will be used as arguments to the RCS "ci" command that
3341 -t./CVS/file,t" to create the initial RCS file container.
3345 commit. If the ./CVS/file,t file doesn't exist, RCS prints an error
3356 you only need to turn off RCS keyword expansion.
3358 First you turn off RCS keyword expansion for the initial checkin by
3368 Then mark the RCS file in the Repository so that keyword expansion is
3374 Repository's RCS file, you no longer need the sticky option. You can
3398 Though you can't hurt the internal structure of an RCS file using its
3399 own "rcs" command, you *can* change the underlying RCS files using
3403 RCS "ci" command and experiment on them with "rcs" before blasting any
3411 experts can use it to set up or restore the internal RCS state that
3443 Then I set the RCS "default branch" back to the Vendor branch, the way
3503 Although you can't outdate a physical (RCS) branch point without
3553 and "commit" or raw RCS commands) or by applying an editor directly to
3587 3. Isn't a CVS "checkout" just a bunch of RCS checkouts?
3589 Like much of CVS, a similar RCS concept is used to support a CVS
3590 function. But a CVS checkout is *not* the same as an RCS checkout.
3644 You should be careful not to confuse CVS with RCS and use "checkout"
3645 in the RCS sense. An RCS "checkout" (which is performed by the RCS
3701 8. How can I lock files while I'm working on them the way RCS does?
3708 RCS locks. The program "rcslock.pl" performs this function. It can be
3927 physical branch in the RCS files.
4013 treated like a <branch_tag>, which becomes a symbolic RCS label
4113 If you didn't configure RCS and CVS to use the GNU version of diff,
4132 create "CVS" sub-directories and it removes all the RCS keywords from
4137 2. Why does it remove the RCS keywords so I can't use the "ident" command
4140 It removes the RCS keywords, so that if the recipient of the exported
4141 sources checks them into another set of RCS files (with or without
4142 CVS), and then makes modifications through RCS or CVS commands, the
4155 exported sources with RCS IDs intact (ci -k) so that their changes
4164 3. Can I override the '-kv' flag CVS passes to RCS?
4190 RCS files, such as a "tag" history or a summary of module activities.
4282 in the RCS files. It takes forever and needs to be rewritten.
4372 an RCS file with a single revision on the "Vendor branch." Subsequent
4431 special, "Vendor" branch and your work is kept on the RCS trunk. New
4442 Note that the CVS "Main Branch" and the RCS Main Trunk are not the
4450 as well to move pre-existing RCS files into Repository directories.
4464 The RCS "ci" command, without -u or -l options, will turn your source
4465 file into an RCS (",v") and delete the original source.
4474 Binary files with RCS keywords in them are a problem, since you don't
4488 The RCS "co" command, when it is invoked by a CVS "checkout" or
4490 list of keywords within the file. They are documented in the RCS "co"
4495 character I have inserted to *avoid* expansion here. The only real RCS
4499 If RCS keyword strings show up in a binary file, they will be altered
4500 unless you set the '-ko' option on the RCS files to tell RCS to keep
4519 If you want to leave old RCS keywords as they are, you can use the
4538 Well bubba, "Yarg" hasn't hit the big time yet. Neither RCS nor CVS
4568 go into the RCS sources and make the same change in the table
4578 Use "import -d" to save the current timestamps on the files as the RCS
4663 create ",v" files using the RCS "ci" command and move them directly
4725 Message is the log message to be stored in the RCS files.
4932 The <message> handed to import is used as an RCS log message, but only
5011 To provide an interface to the RCS "rlog" command, which displays
5012 information about the underlying RCS files, including the revision
5013 history and Tag (RCS calls it a "symbol") list.
5030 (If <rev1> is a numeric RCS symbol attached to a branch revision with
5044 the RCS "rlog" (and therefore the "cvs log") command will
5072 4. How do I generate ChangeLogs from RCS logs?
5087 RCS file dates are stored in GMT to allow users in different time
5094 timezone information in all the time stamps, but that changes the RCS
5096 few RCS releases.
5472 filename in the line beginning with "RCS version:", which is not
5497 To add a symbolic label (a "tag") to the RCS files last checked out,
5961 RCS file.
6098 versions 2.0 and 2.1 that causes RCS versions before 5.6.0.1 to fail
6103 Go back to using GNU diff 1.15 or 2.0 with RCS versions 5.5 or 5.6.
6107 Grab RCS version 5.6.0.1 from an FSF archive and set the DIFF3_A
6112 Patch the RCS 5.6 source. Change line 84 in "merger.c" from:
6117 Wait both for RCS version 5.7 to be released and for a new version
6171 <eggert@twinsun.com>, RCS maintainer.
6249 If careful testing reveals an RCS bug rather than a CVS bug, you can
6485 RCS file: /Repository/module/<file> retrieving revision 1.X retrieving
6499 RCS file: /Repository/module/<file> retrieving revision 1.X retrieving
6593 command (mostly RCS commands and file deletions) it executes. When
6985 You won't hurt the underlying RCS files and if you are executing a
6991 usually some form of RCS command.
7016 an RCS checkin, RCS will leave the file either fully
7031 commit them. It helps that RCS doesn't leave a file in an
7038 "commit". The RCS file will still be consistent, but
7039 unlike "commit", which only *adds* to the RCS file, "tag"
7149 variable mentioned below, then the RCS commands
7167 RCSBIN Changes where CVS finds the RCS commands.
7200 5. I have been using RCS for a while. Can I convert to CVS without losing
7276 Copy the RCS (",v") file directly in the Repository.
7416 Copy the RCS (",v") files directly in the Repository, creating the
7480 1. How does CVS differ from RCS?
7482 CVS uses RCS to do much of its work and absolutely all the work of
7483 changing the underlying RCS files in the Repository.
7485 RCS comprises a set of programs designed to keep track of changes to
7492 you to treat a collection of RCS files as a single object. Of course,
7499 not the same as an RCS branch. To support a CVS branch, CVS uses
7500 "tags" (what RCS calls "symbols") and some local state, in addition to
7501 RCS branches.
7503 Other features offered by CVS that are not supported directly by RCS
7517 old data, it is less likely than when using raw RCS.
7525 SCCS is much closer to RCS than to CVS, so some of the previous entry
7528 You might want to take a look at Walter Tichy's papers on RCS, which
7529 are referred to in the RCS man pages.
7570 provided. Like RCS, ClearCase supports branches, symbolic tags, and
7572 converters from RCS, SCCS, DSEE formats are also included.
7631 sub-programs (make, RCS, etc.) to implement pieces of the imposed
7649 file. Files are version controlled in a manner similar to RCS.
7764 PVCS works on single files like RCS and SCCS, CVS works on complete
7802 files and all the RCS files that constitute "imported" or "committed"
7821 2. What is an RCS file?
7823 An RCS file is a text file containing the source text and the revision
7828 RCS is the "Revision Control System" that CVS uses to manage
7829 individual files. RCS file names normally end in ",v", but that can be
7830 altered (via the RCS -x option) to conform to file naming standards on
7903 particular revision from a set of RCS files into your working area.
7915 in", in RCS terms) some time in the past. CVS (and RCS) can retrieve
7917 "tag" ("symbolic name", in RCS terms).
7936 The CVS "Tag" is implemented by applying RCS "symbols" to each
7986 the RCS Main branch before the "import" is complete.
8024 RCS branches) is the same as in a development branch, its purpose and
8046 Another name for the RCS Main Branch. The RCS Main Branch is related,
8124 of a common starting file. Checking out an RCS revision produces a
8205 CVS saves its version-control information in RCS files stored in a
8209 Files in the Repository are stored in a format dictated by the RCS
8210 commands CVS uses to do much of its real work. RCS files are standard
8250 The major advantage of using CVS over the simpler tools like RCS or
8408 for RCS. If you are a programmer, you can also read the source code to
8481 RCS 5.7 (latest version available today)
8485 The GNU version of diff is suggested by both the RCS and CVS
8489 It is a good idea not to accept the versions of CVS, RCS or diff you